docs(package name): use @SvelteStack instead of @TanStack

Author: amen-souissi

docs/src/pages/guides/background-fetching-indicators.md

@@ -7,7 +7,7 @@ A query's `status === 'loading'` state is sufficient enough to show the initial
 
 ```markdown
 <script>
-  import { useQuery } from '@tanstack/svelte-query';
+  import { useQuery } from '@sveltestack/svelte-query';
 
   const queryResult = useQuery('todos', fetchTodos)
 </script>
@@ -32,7 +32,7 @@ In addition to individual query loading states, if you would like to show a glob
 
 ```markdown
 <script>
-  import { useIsFetching } from '@tanstack/svelte-query'
+  import { useIsFetching } from '@sveltestack/svelte-query'
 
   const isFetching = useIsFetching()
 </script>

docs/src/pages/guides/default-query-function.md

@@ -7,7 +7,7 @@ If you find yourself wishing for whatever reason that you could just share the s
 
 ```markdown
 <script>
-  import { QueryClientProvider } from '@tanstack/svelte-query';
+  import { QueryClientProvider } from '@sveltestack/svelte-query';
   // Define a default query function that will receive the query key
   const defaultQueryFn = async ({ queryKey }) => {
     const { data } = await axios.get(`https://jsonplaceholder.typicode.com${queryKey[0]}`)

docs/src/pages/guides/infinite-queries.md

@@ -41,7 +41,7 @@ With this information, we can create a "Load More" UI by:
 
 ```markdown
 <script>
-  import { useInfiniteQuery } from '@tanstack/svelte-query'
+  import { useInfiniteQuery } from '@sveltestack/svelte-query'
 
   const fetchProjects = async ({ pageParam = 0 }) => {
     const { data } = await axios.get(`/projects?cursor=${pageParam}`)
@@ -90,7 +90,7 @@ By default, the variable returned from `getNextPageParam` will be supplied to th
 
 ```markdown
 <script>
-  import { useInfiniteQuery } from '@tanstack/svelte-query'
+  import { useInfiniteQuery } from '@sveltestack/svelte-query'
 
   const fetchProjects = async ({ pageParam = 0 }) => {
     const { data } = await axios.get(`/projects?cursor=${pageParam}`)

docs/src/pages/guides/invalidations-from-mutations.md

@@ -14,7 +14,7 @@ const mutation = useMutation(postTodo)
 When a successful `postTodo` mutation happens, we likely want all `todos` queries to get invalidated and possibly refetched to show the new todo item. To do this, you can use `useMutation`'s `onSuccess` options and the `client`'s `invalidateQueries` function:
 
 ```js
-import { useMutation, useQueryClient } from '@tanstack/svelte-query'
+import { useMutation, useQueryClient } from '@sveltestack/svelte-query'
 
 const queryClient = useQueryClient()
 

docs/src/pages/guides/mutations.md

@@ -9,7 +9,7 @@ Here's an example of a mutation that adds a new todo the server:
 
 ```markdown
 <script>
-  import { useMutation } from '@tanstack/svelte-query'
+  import { useMutation } from '@sveltestack/svelte-query'
 
   const mutation = useMutation(newTodo => axios.post('/todos', newTodo))
 </script>

docs/src/pages/guides/queries.md

@@ -15,7 +15,7 @@ To subscribe to a query in your components or custom hooks, call the `useQuery`
   - Throws an error
 
 ```js
-import { useQuery } from '@tanstack/svelte-query'
+import { useQuery } from '@sveltestack/svelte-query'
 
 const info = useQuery('todos', fetchTodoList)
 ```
@@ -46,7 +46,7 @@ For **most** queries, it's usually sufficient to check for the `isLoading` state
 ```markdown
 
 <script>
-  import { useQuery } from '@tanstack/svelte-query';
+  import { useQuery } from '@sveltestack/svelte-query';
 
   const queryResult = useQuery('todos', fetchTodos)
 </script>
@@ -69,7 +69,7 @@ If booleans aren't your thing, you can always use the `status` state as well:
 
 ```markdown
 <script>
-  import { useQuery } from '@tanstack/svelte-query';
+  import { useQuery } from '@sveltestack/svelte-query';
 
   const queryResult = useQuery('todos', fetchTodos)
 </script>

docs/src/pages/guides/query-functions.md

@@ -68,7 +68,7 @@ function fetchTodoList({ queryKey }) {
 Anywhere the `[queryKey, queryFn, config]` signature is supported throughout Svelte Query's API, you can also use an object to express the same configuration:
 
 ```js
-import { useQuery } from '@tanstack/svelte-query'
+import { useQuery } from '@sveltestack/svelte-query'
 
 useQuery({
   queryKey: ['todo', 7],

docs/src/pages/guides/query-invalidation.md

@@ -26,7 +26,7 @@ When using APIs like `invalidateQueries` and `removeQueries` (and others that su
 In this example, we can use the `todos` prefix to invalidate any queries that start with `todos` in their query key:
 
 ```js
-import { useQuery, useQueryClient } from '@tanstack/svelte-query'
+import { useQuery, useQueryClient } from '@sveltestack/svelte-query'
 
 // Get QueryClient from the context
 const queryClient = useQueryClient()

docs/src/pages/guides/query-retries.md

@@ -13,7 +13,7 @@ You can configure retries both on a global level and an individual query level.
 - Setting `retry = (failureCount, error) => ...` allows for custom logic based on why the request failed.
 
 ```js
-import { useQuery } from '@tanstack/svelte-query'
+import { useQuery } from '@sveltestack/svelte-query'
 
 // Make a specific query retry a certain number of times
 const queryResult = useQuery(['todos', 1], fetchTodoListPage, {
@@ -30,7 +30,7 @@ The default `retryDelay` is set to double (starting at `1000`ms) with each attem
 ```markdown
 <script>
 // Configure for all queries
-import { QueryCache, QueryClient, QueryClientProvider } from '@tanstack/svelte-query'
+import { QueryCache, QueryClient, QueryClientProvider } from '@sveltestack/svelte-query'
 
 const queryClient = new QueryClient({
   defaultOptions: {

docs/src/pages/guides/window-focus-refetching.md

@@ -10,7 +10,7 @@ If a user leaves your application and returns to stale data, **Svelte Query auto
 ```markdown
 <script>
 // Configure for all queries
-import { QueryClient, QueryClientProvider } from '@tanstack/svelte-query'
+import { QueryClient, QueryClientProvider } from '@sveltestack/svelte-query'
 
 const queryClient = new QueryClient({
   defaultOptions: {
@@ -56,7 +56,7 @@ focusManager.setEventListener(handleFocus => {
 A great use-case for replacing the focus handler is that of iframe events. Iframes present problems with detecting window focus by both double-firing events and also firing false-positive events when focusing or using iframes within your app. If you experience this, you should use an event handler that ignores these events as much as possible. I recommend [this one](https://gist.github.com/tannerlinsley/1d3a2122332107fcd8c9cc379be10d88)! It can be set up in the following way:
 
 ```js
-import { focusManager } from '@tanstack/svelte-query'
+import { focusManager } from '@sveltestack/svelte-query'
 import onWindowFocus from './onWindowFocus' // The gist above
 
 focusManager.setEventListener(onWindowFocus) // Boom!
@@ -65,7 +65,7 @@ focusManager.setEventListener(onWindowFocus) // Boom!
 ## Managing focus state
 
 ```js
-import { focusManager } from '@tanstack/svelte-query'
+import { focusManager } from '@sveltestack/svelte-query'
 
 // Override the default focus state
 focusManager.setFocused(true)