Packages

@pinia/colada

1.4.9 · 30 Oct 2026MIT207.8k / weekRepositoryHomepagenpmAtom feed

Your version

83 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 0.13.x
  2. 0.13.6

    12 Feb 2025
    • Add devtools

    • Apply multiple filters to getEntries

  3. 0.13.5

    6 Feb 2025
    • Add experimental useInfiniteQuery

    • Avoid clearing timeouts early

    • Correctly track new define queries when switching pages

  4. 0.13.4

    31 Jan 2025
    • plugins: toCacheKey

    • types: expose QueryCache

  5. 0.13.3

    14 Jan 2025
    • query: always use placeholderData (4c6a3f7), closes #154

    • query: avoid creating entries after unmounting (e2ff278), closes #155

  6. 0.13.2

    3 Jan 2025
  7. 0.13.1

    20 Dec 2024
    • Do not run disabled defined queries on mount (a85ac9f), closes #138

  8. 0.13.0

    26 Nov 2024
    • Breaking

      types: placeholderData no longer allows returning null, only undefined. This won't affect most use cases and enables better type inference.

    • types: remove undefined with initialData and placeholderData

  9. 0.12.x
  10. 0.12.1

    9 Nov 2024
    • staleTime of Infinity should still be stale

  11. 0.12.0

    6 Nov 2024
    • Breaking

      transformError was never fully implemented so they are being removed and might come back if they is a real-word use case for them

    • Breaking

      If you were using the delayLoadingRef util, use the @pinia/colada-plugin-delay instead.

    • Breaking

      Renaming Error to defaultError allows to differentiate the property from the existing global Error class. Upgrading should be straightforward.

  12. 0.11.x
  13. 0.11.1

    28 Oct 2024
    • Allow refetches to throw on erorr

    • Allow setting data for unexisting queries

    • Allow gcTime to never be set

  14. 0.11.0

    25 Oct 2024
    • Breaking

      mutations: This wasn't needed as instead, one can use useQueryCache() outside. It could be added back if needed but it's more pragmatic to start without it.

    • Breaking

      query: The queryCache.cancelQuery() is renamed to queryCache.cancel() to better match the other functions naming. A new function queryCache.cancelQueries() is added to actually cancel one or multiple queries instead of just one.

    • Breaking

      plugins: In plugins, cache is renamed to queryCache for consistency.

  15. 0.10.x
  16. 0.10.0

    4 Oct 2024
    • Breaking

      This change is mainly to simplify migration from TanStack Query.

    • Breaking

      Caches.invalidateQueries only fetches active queries

    • Breaking

      The keys option that automatically invalidate keys has been renamed to invalidateKeys and moved to a plugin. This is in practice not needed. It's just an opinionated convenience that can be replaced by directly invalidating queries in the cache with the onSettled() hook in useMutation():

  17. 0.9.x
  18. 0.9.1

    27 Sep 2024
    • Allow nullish return in placeholderData

    • Wip nuxt module

    • Wip placeholderData

  19. 0.9.0

    26 Aug 2024
    • Breaking

      query-cache: To better match the arguments, the setQueryState action has been renamed to setEntryState.

    • mutations: add variables

    • query-cache: Rename setQueryState to setEntryState

  20. 0.8.x
  21. 0.8.2

    21 Aug 2024
    • Skip reactivity traversal in store

  22. 0.8.1

    17 Aug 2024
    • ssr: expose reviveTreeMap

    • ssr: mark raw tree node in reviver

  23. 0.8.0

    12 Aug 2024
    • Breaking

      isFetching from useQuery() is renamed to isLoading to better reflect that it's connected to asyncStatus.

    • Breaking

      The setup option in useQuery now receives the options as the second argument instead of a context object with the query return value and the options. This allows the setup function to have a more predictable signature and makes it easier to type. Only PiniaColada has this option, it has been removed from useQuery. Overall, the option still needs more thinking and will probably change in the future again.

    • Breaking

      plugins: The onSuccess, onError, and onSettled global hooks have been moved from PiniaPlugin to a Pinia Colada plugin: PiniaColadaQueryHooksPlugin

       app.use(PiniaColada, {
      +  plugins: [
      +    PiniaColadaQueryHooksPlugin({
             onSuccess() {},
             onError() {},
             onSettled() {},
      +    }),
      +  ],
       })
  24. 0.7.x
  25. 0.7.1

    30 Jul 2024
    • hmr: always update options

  26. 0.7.0

    26 Jul 2024
    • Breaking

      Rename type UseEntryKey to EntryKey

    • Breaking

      The exported type 'UseQueryKey' is replaced by the more generic type 'UseEntryKey', which will be also used to type mutations

    • Deprecated

      Support plugins and deprecate QueryPlugin in favor of PiniaColada

  27. 0.6.x
  28. 0.6.0

    2 Apr 2024
    • Breaking

      mutation: Rename type UseQueryStatus to QueryStatus

    • Breaking

      mutation: mutate no longer returns a promise and catches errors to be safely used in templates. The old behavior remains the same with mutateAsync

    • Breaking

      mutation: the mutation option in useMutation() now only accepts one argument for the variables. This allows to add extra parameters in the future like a signal, an extra context, etc

  29. 0.5.x
  30. 0.5.3

    21 Feb 2024
    • onScopeDispose guard

  31. 0.5.2

    20 Feb 2024
    • Allow writing to entries

  32. 0.5.1

    19 Feb 2024
    • types: allow default error type

    • Avoid computed warns

  33. 0.5.0

    19 Feb 2024
    • Breaking

      Remove internal global defaults

    • Breaking

      Force array of keys to avoid easy mistakes

    • Pass signal to query

  34. 0.4.x
  35. 0.4.3

    11 Feb 2024
    • Add delayLoadingRef

  36. 0.4.2

    8 Feb 2024
    • Avoid warn onScopeDispose

  37. 0.4.1

    7 Feb 2024
  38. 0.4.0

    6 Feb 2024
    • Breaking

      Rename data fetching store

    • Breaking

      Replace class usage

    • Breaking

      Add QueryPlugin to configure useQuery()

  39. 0.3.x
  40. 0.3.1

    3 Feb 2024
    • useMutation: options

  41. 0.3.0

    3 Feb 2024
    • Breaking

      The option fetcher for useQuery() has been renamed to query. The option mutator for useMutation() has been renamed mutation.

  42. 0.2.x
  43. 0.2.0

    16 Jan 2024
    • Breaking

      Remove iife version

    • Accept function in setEntryData

    • Allow array of keys

  44. 0.1.x
  45. 0.1.0

    25 Dec 2023
    • Breaking

      Rename options

    • Swallow error in automatic refreshes

  46. 0.0.x
  47. 0.0.1

    20 Dec 2023
    • Initial version

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.