{"id":15311656,"url":"https://github.com/aslemammad/zustand","last_synced_at":"2025-10-08T20:32:49.539Z","repository":{"id":105999074,"uuid":"407769545","full_name":"Aslemammad/zustand","owner":"Aslemammad","description":"🐻 Bear necessities for state management in React","archived":false,"fork":true,"pushed_at":"2022-04-18T01:16:41.000Z","size":5292,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"main","last_synced_at":"2024-09-30T10:32:34.071Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://zustand.surge.sh","language":null,"has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"pmndrs/zustand","license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Aslemammad.png","metadata":{"files":{"readme":"readme.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null}},"created_at":"2021-09-18T05:51:58.000Z","updated_at":"2022-02-08T09:02:32.000Z","dependencies_parsed_at":null,"dependency_job_id":"89e17f40-d28f-4077-9fd8-cb927e1fa2e9","html_url":"https://github.com/Aslemammad/zustand","commit_stats":{"total_commits":481,"total_committers":76,"mean_commits":6.328947368421052,"dds":0.5966735966735967,"last_synced_commit":"2a412500f5fb29661291f099e100ee1c6a721573"},"previous_names":[],"tags_count":52,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Aslemammad%2Fzustand","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Aslemammad%2Fzustand/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Aslemammad%2Fzustand/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Aslemammad%2Fzustand/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Aslemammad","download_url":"https://codeload.github.com/Aslemammad/zustand/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":219877266,"owners_count":16554910,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-01T08:34:14.561Z","updated_at":"2025-10-08T20:32:44.189Z","avatar_url":"https://github.com/Aslemammad.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003cp align=\"center\"\u003e\n  \u003cimg src=\"bear.jpg\" /\u003e\n\u003c/p\u003e\n\n[![Build Status](https://img.shields.io/github/workflow/status/pmndrs/zustand/Lint?style=flat\u0026colorA=000000\u0026colorB=000000)](https://github.com/pmndrs/zustand/actions?query=workflow%3ALint)\n[![Build Size](https://img.shields.io/bundlephobia/min/zustand?label=bundle%20size\u0026style=flat\u0026colorA=000000\u0026colorB=000000)](https://bundlephobia.com/result?p=zustand)\n[![Version](https://img.shields.io/npm/v/zustand?style=flat\u0026colorA=000000\u0026colorB=000000)](https://www.npmjs.com/package/zustand)\n[![Downloads](https://img.shields.io/npm/dt/zustand.svg?style=flat\u0026colorA=000000\u0026colorB=000000)](https://www.npmjs.com/package/zustand)\n[![Discord Shield](https://img.shields.io/discord/740090768164651008?style=flat\u0026colorA=000000\u0026colorB=000000\u0026label=discord\u0026logo=discord\u0026logoColor=ffffff)](https://discord.gg/poimandres)\n\nA small, fast and scalable bearbones state-management solution using simplified flux principles. Has a comfy api based on hooks, isn't boilerplatey or opinionated.\n\nDon't disregard it because it's cute. It has quite the claws, lots of time was spent to deal with common pitfalls, like the dreaded [zombie child problem](https://react-redux.js.org/api/hooks#stale-props-and-zombie-children), [react concurrency](https://github.com/bvaughn/rfcs/blob/useMutableSource/text/0000-use-mutable-source.md), and [context loss](https://github.com/facebook/react/issues/13332) between mixed renderers. It may be the one state-manager in the React space that gets all of these right.\n\nYou can try a live demo [here](https://codesandbox.io/s/dazzling-moon-itop4).\n\n```bash\nnpm install zustand # or yarn add zustand\n```\n\n## First create a store\n\nYour store is a hook! You can put anything in it: primitives, objects, functions. The `set` function *merges* state.\n\n```jsx\nimport create from 'zustand'\n\nconst useStore = create(set =\u003e ({\n  bears: 0,\n  increasePopulation: () =\u003e set(state =\u003e ({ bears: state.bears + 1 })),\n  removeAllBears: () =\u003e set({ bears: 0 })\n}))\n```\n\n## Then bind your components, and that's it!\n\nUse the hook anywhere, no providers needed. Select your state and the component will re-render on changes.\n\n```jsx\nfunction BearCounter() {\n  const bears = useStore(state =\u003e state.bears)\n  return \u003ch1\u003e{bears} around here ...\u003c/h1\u003e\n}\n\nfunction Controls() {\n  const increasePopulation = useStore(state =\u003e state.increasePopulation)\n  return \u003cbutton onClick={increasePopulation}\u003eone up\u003c/button\u003e\n}\n```\n\n### Why zustand over redux?\n\n* Simple and un-opinionated\n* Makes hooks the primary means of consuming state\n* Doesn't wrap your app in context providers\n* [Can inform components transiently (without causing render)](#transient-updates-for-often-occuring-state-changes)\n\n### Why zustand over context?\n\n* Less boilerplate\n* Renders components only on changes\n* Centralized, action-based state management\n\n---\n\n# Recipes\n\n## Fetching everything\n\nYou can, but bear in mind that it will cause the component to update on every state change!\n\n```jsx\nconst state = useStore()\n```\n\n## Selecting multiple state slices\n\nIt detects changes with strict-equality (old === new) by default, this is efficient for atomic state picks.\n\n```jsx\nconst nuts = useStore(state =\u003e state.nuts)\nconst honey = useStore(state =\u003e state.honey)\n```\n\nIf you want to construct a single object with multiple state-picks inside, similar to redux's mapStateToProps, you can tell zustand that you want the object to be diffed shallowly by passing the `shallow` equality function.\n\n```jsx\nimport shallow from 'zustand/shallow'\n\n// Object pick, re-renders the component when either state.nuts or state.honey change\nconst { nuts, honey } = useStore(state =\u003e ({ nuts: state.nuts, honey: state.honey }), shallow)\n\n// Array pick, re-renders the component when either state.nuts or state.honey change\nconst [nuts, honey] = useStore(state =\u003e [state.nuts, state.honey], shallow)\n\n// Mapped picks, re-renders the component when state.treats changes in order, count or keys\nconst treats = useStore(state =\u003e Object.keys(state.treats), shallow)\n```\n\nFor more control over re-rendering, you may provide any custom equality function.\n\n```jsx\nconst treats = useStore(\n  state =\u003e state.treats,\n  (oldTreats, newTreats) =\u003e compare(oldTreats, newTreats)\n)\n```\n\n## Memoizing selectors\n\nIt is generally recommended to memoize selectors with useCallback. This will prevent unnecessary computations each render. It also allows React to optimize performance in concurrent mode.\n\n```jsx\nconst fruit = useStore(useCallback(state =\u003e state.fruits[id], [id]))\n```\n\nIf a selector doesn't depend on scope, you can define it outside the render function to obtain a fixed reference without useCallback.\n\n```jsx\nconst selector = state =\u003e state.berries\n\nfunction Component() {\n  const berries = useStore(selector)\n```\n\n## Overwriting state\n\nThe `set` function has a second argument, `false` by default. Instead of merging, it will replace the state model. Be careful not to wipe out parts you rely on, like actions.\n\n```jsx\nimport omit from \"lodash-es/omit\"\n\nconst useStore = create(set =\u003e ({\n  salmon: 1,\n  tuna: 2,\n  deleteEverything: () =\u003e set({ }, true), // clears the entire store, actions included\n  deleteTuna: () =\u003e set(state =\u003e omit(state, ['tuna']), true)\n}))\n```\n\n## Async actions\n\nJust call `set` when you're ready, zustand doesn't care if your actions are async or not.\n\n```jsx\nconst useStore = create(set =\u003e ({\n  fishies: {},\n  fetch: async pond =\u003e {\n    const response = await fetch(pond)\n    set({ fishies: await response.json() })\n  }\n}))\n```\n\n## Read from state in actions\n\n`set` allows fn-updates `set(state =\u003e result)`, but you still have access to state outside of it through `get`.\n\n```jsx\nconst useStore = create((set, get) =\u003e ({\n  sound: \"grunt\",\n  action: () =\u003e {\n    const sound = get().sound\n    // ...\n  }\n})\n```\n\n## Reading/writing state and reacting to changes outside of components\n\nSometimes you need to access state in a non-reactive way, or act upon the store. For these cases the resulting hook has utility functions attached to its prototype.\n\n```jsx\nconst useStore = create(() =\u003e ({ paw: true, snout: true, fur: true }))\n\n// Getting non-reactive fresh state\nconst paw = useStore.getState().paw\n// Listening to all changes, fires on every change\nconst unsub1 = useStore.subscribe(console.log)\n// Listening to selected changes, in this case when \"paw\" changes\nconst unsub2 = useStore.subscribe(console.log, state =\u003e state.paw)\n// Subscribe also supports an optional equality function\nconst unsub3 = useStore.subscribe(console.log, state =\u003e [state.paw, state.fur], shallow)\n// Subscribe also exposes the previous value\nconst unsub4 = useStore.subscribe((paw, previousPaw) =\u003e console.log(paw, previousPaw), state =\u003e state.paw)\n// Updating state, will trigger listeners\nuseStore.setState({ paw: false })\n// Unsubscribe listeners\nunsub1()\nunsub2()\nunsub3()\nunsub4()\n// Destroying the store (removing all listeners)\nuseStore.destroy()\n\n// You can of course use the hook as you always would\nfunction Component() {\n  const paw = useStore(state =\u003e state.paw)\n```\n\n## Using zustand without React\n\nZustands core can be imported and used without the React dependency. The only difference is that the create function does not return a hook, but the api utilities.\n\n```jsx\nimport create from 'zustand/vanilla'\n\nconst store = create(() =\u003e ({ ... }))\nconst { getState, setState, subscribe, destroy } = store\n```\n\nYou can even consume an existing vanilla store with React:\n\n```jsx\nimport create from 'zustand'\nimport vanillaStore from './vanillaStore'\n\nconst useStore = create(vanillaStore)\n```\n\n:warning: Note that middlewares that modify `set` or `get` are not applied to `getState` and `setState`.\n\n## Transient updates (for often occuring state-changes)\n\nThe subscribe function allows components to bind to a state-portion without forcing re-render on changes. Best combine it with useEffect for automatic unsubscribe on unmount. This can make a [drastic](https://codesandbox.io/s/peaceful-johnson-txtws) performance impact when you are allowed to mutate the view directly.\n\n```jsx\nconst useStore = create(set =\u003e ({ scratches: 0, ... }))\n\nfunction Component() {\n  // Fetch initial state\n  const scratchRef = useRef(useStore.getState().scratches)\n  // Connect to the store on mount, disconnect on unmount, catch state-changes in a reference\n  useEffect(() =\u003e useStore.subscribe(\n    scratches =\u003e (scratchRef.current = scratches),\n    state =\u003e state.scratches\n  ), [])\n```\n\n## Sick of reducers and changing nested state? Use Immer!\n\nReducing nested structures is tiresome. Have you tried [immer](https://github.com/mweststrate/immer)?\n\n```jsx\nimport produce from 'immer'\n\nconst useStore = create(set =\u003e ({\n  lush: { forest: { contains: { a: \"bear\" } } },\n  clearForest: () =\u003e set(produce(state =\u003e {\n    state.lush.forest.contains = null\n  }))\n}))\n\nconst clearForest = useStore(state =\u003e state.clearForest)\nclearForest();\n```\n\n## Middleware\n\nYou can functionally compose your store any way you like.\n\n```jsx\n// Log every time state is changed\nconst log = config =\u003e (set, get, api) =\u003e config(args =\u003e {\n  console.log(\"  applying\", args)\n  set(args)\n  console.log(\"  new state\", get())\n}, get, api)\n\n// Turn the set method into an immer proxy\nconst immer = config =\u003e (set, get, api) =\u003e config((partial, replace) =\u003e {\n  const nextState = typeof partial === 'function'\n      ? produce(partial)\n      : partial\n  return set(nextState, replace)\n}, get, api)\n\nconst useStore = create(\n  log(\n    immer((set) =\u003e ({\n      bees: false,\n      setBees: (input) =\u003e set((state) =\u003e void (state.bees = input)),\n    })),\n  ),\n)\n```\n\n\u003cdetails\u003e\n\u003csummary\u003eHow to pipe middlewares\u003c/summary\u003e\n\n```js\nimport create from \"zustand\"\nimport produce from \"immer\"\nimport pipe from \"ramda/es/pipe\"\n\n/* log and immer functions from previous example */\n/* you can pipe as many middlewares as you want */\nconst createStore = pipe(log, immer, create)\n\nconst useStore = createStore(set =\u003e ({\n  bears: 1,\n  increasePopulation: () =\u003e set(state =\u003e ({ bears: state.bears + 1 }))\n}))\n\nexport default useStore\n```\nFor a TS example see the following [discussion](https://github.com/pmndrs/zustand/discussions/224#discussioncomment-118208)\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003eHow to type immer middleware in TypeScript\u003c/summary\u003e\n\n```ts\nimport { State, StateCreator } from 'zustand'\nimport produce, { Draft } from 'immer'\n\nconst immer = \u003cT extends State\u003e(config: StateCreator\u003cT\u003e): StateCreator\u003cT\u003e =\u003e \n  (set, get, api) =\u003e config((partial, replace) =\u003e {\n    const nextState =\n      typeof partial === 'function'\n        ? produce(partial as (state: Draft\u003cT\u003e) =\u003e T)\n        : partial as T\n    return set(nextState, replace)\n  }, get, api)\n```\n\n\u003c/details\u003e\n\n## Persist middleware\n\nYou can persist your store's data using any kind of storage.\n\n```jsx\nimport create from \"zustand\"\nimport { persist } from \"zustand/middleware\"\n\nexport const useStore = create(persist(\n  (set, get) =\u003e ({\n    fishes: 0,\n    addAFish: () =\u003e set({ fishes: get().fishes + 1 })\n  }),\n  {\n    name: \"food-storage\", // unique name\n    getStorage: () =\u003e sessionStorage, // (optional) by default the 'localStorage' is used\n  }\n))\n```\n\n\u003cdetails\u003e\n\u003csummary\u003eHow to use custom storage engines\u003c/summary\u003e\n\nYou can use other storage methods outside of `localStorage` and `sessionStorage` by defining your own `StateStorage`. A custom `StateStorage` object also allows you to write middlware for the persisted store when getting or setting store data.\n\n```tsx\nimport create from \"zustand\"\nimport { persist, StateStorage } from \"zustand/middleware\"\nimport { get, set } from 'idb-keyval' // can use anything: IndexedDB, Ionic Storage, etc.\n\n// Custom storage object\nconst storage: StateStorage = {\n  getItem: async (name: string): Promise\u003cstring | null\u003e =\u003e {\n    console.log(name, \"has been retrieved\");\n    return await get(name) || null\n  },\n  setItem: async (name: string, value: string): Promise\u003cvoid\u003e =\u003e {\n    console.log(name, \"with value\", value, \"has been saved\");\n    set(name, value)\n  }\n}\n\nexport const useStore = create(persist(\n  (set, get) =\u003e ({\n    fishes: 0,\n    addAFish: () =\u003e set({ fishes: get().fishes + 1 })\n  }),\n  {\n    name: \"food-storage\", // unique name\n    getStorage: () =\u003e storage,\n  }\n))\n```\n\n\u003c/details\u003e\n\n## Can't live without redux-like reducers and action types?\n\n```jsx\nconst types = { increase: \"INCREASE\", decrease: \"DECREASE\" }\n\nconst reducer = (state, { type, by = 1 }) =\u003e {\n  switch (type) {\n    case types.increase: return { grumpiness: state.grumpiness + by }\n    case types.decrease: return { grumpiness: state.grumpiness - by }\n  }\n}\n\nconst useStore = create(set =\u003e ({\n  grumpiness: 0,\n  dispatch: args =\u003e set(state =\u003e reducer(state, args)),\n}))\n\nconst dispatch = useStore(state =\u003e state.dispatch)\ndispatch({ type: types.increase, by: 2 })\n```\n\nOr, just use our redux-middleware. It wires up your main-reducer, sets initial state, and adds a dispatch function to the state itself and the vanilla api. Try [this](https://codesandbox.io/s/amazing-kepler-swxol) example.\n\n```jsx\nimport { redux } from 'zustand/middleware'\n\nconst useStore = create(redux(reducer, initialState))\n```\n\n## Calling actions outside a React event handler\n\nBecause React handles `setState` synchronously if it's called outside an event handler. Updating the state outside an event handler will force react to update the components synchronously, therefore adding the risk of encountering the zombie-child effect.\nIn order to fix this, the action needs to be wrapped in `unstable_batchedUpdates`\n\n```jsx\nimport { unstable_batchedUpdates } from 'react-dom' // or 'react-native'\n\nconst useStore = create((set) =\u003e ({\n  fishes: 0,\n  increaseFishes: () =\u003e set((prev) =\u003e ({ fishes: prev.fishes + 1 }))\n}))\n\nconst nonReactCallback = () =\u003e {\n  unstable_batchedUpdates(() =\u003e {\n    useStore.getState().increaseFishes()\n  })\n}\n```\n\nMore details: https://github.com/pmndrs/zustand/issues/302\n\n## Redux devtools\n\n```jsx\nimport { devtools } from 'zustand/middleware'\n\n// Usage with a plain action store, it will log actions as \"setState\"\nconst useStore = create(devtools(store))\n// Usage with a redux store, it will log full action types\nconst useStore = create(devtools(redux(reducer, initialState)))\n```\n\ndevtools takes the store function as its first argument, optionally you can name the store or configure [serialize](https://github.com/zalmoxisus/redux-devtools-extension/blob/master/docs/API/Arguments.md#serialize) options with a second argument.  \n  \nName store: `devtools(store, {name: \"MyStore\"})`, which will be prefixed to your actions.  \nSerialize options: `devtools(store, { serialize: { options: true } })`.  \n  \ndevtools will only log actions from each separated store unlike in a typical *combined reducers* redux store. See an approach to combining stores https://github.com/pmndrs/zustand/issues/163\n\n## React context\n\nThe store created with `create` doesn't require context providers. In some cases, you may want to use contexts for dependency injection or if you want to initialize your store with props from a component. Because the store is a hook, passing it as a normal context value may violate rules of hooks. To avoid misusage, a special `createContext` is provided.\n\n```jsx\nimport create from 'zustand'\nimport createContext from 'zustand/context'\n\nconst { Provider, useStore } = createContext()\n\nconst createStore = () =\u003e create(...)\n\nconst App = () =\u003e (\n  \u003cProvider createStore={createStore}\u003e\n    ...\n  \u003c/Provider\u003e\n)\n\nconst Component = () =\u003e {\n  const state = useStore()\n  const slice = useStore(selector)\n  ...\n}\n```\n\u003cdetails\u003e\n  \u003csummary\u003ecreateContext usage in real components\u003c/summary\u003e\n\n  ```jsx\n  import create from \"zustand\";\n  import createContext from \"zustand/context\";\n\n  // Best practice: You can move the below createContext() and createStore to a separate file(store.js) and import the Provider, useStore here/wherever you need.\n\n  const { Provider, useStore } = createContext();\n\n  const createStore = () =\u003e\n    create((set) =\u003e ({\n      bears: 0,\n      increasePopulation: () =\u003e set((state) =\u003e ({ bears: state.bears + 1 })),\n      removeAllBears: () =\u003e set({ bears: 0 })\n    }));\n\n  const Button = () =\u003e {\n    return (\n        {/** store() - This will create a store for each time using the Button component instead of using one store for all components **/}\n      \u003cProvider createStore={createStore}\u003e \n        \u003cButtonChild /\u003e\n      \u003c/Provider\u003e\n    );\n  };\n\n  const ButtonChild = () =\u003e {\n    const state = useStore();\n    return (\n      \u003cdiv\u003e\n        {state.bears}\n        \u003cbutton\n          onClick={() =\u003e {\n            state.increasePopulation();\n          }}\n        \u003e\n          +\n        \u003c/button\u003e\n      \u003c/div\u003e\n    );\n  };\n\n  export default function App() {\n    return (\n      \u003cdiv className=\"App\"\u003e\n        \u003cButton /\u003e\n        \u003cButton /\u003e\n      \u003c/div\u003e\n    );\n  }\n  ```\n\u003c/details\u003e\n\n\u003cdetails\u003e\n  \u003csummary\u003ecreateContext usage with initialization from props (in TypeScript)\u003c/summary\u003e\n\n  ```tsx\n  import create from \"zustand\";\n  import createContext from \"zustand/context\";\n\n  type BearState = {\n    bears: number\n    increase: () =\u003e void\n  }\n\n  // pass the type to `createContext` rather than to `create`\n  const { Provider, useStore } = createContext\u003cBearState\u003e();\n\n  export default function App({ initialBears }: { initialBears: number }) {\n    return (\n      \u003cProvider\n        createStore={() =\u003e\n          create((set) =\u003e ({\n            bears: initialBears,\n            increase: () =\u003e set((state) =\u003e ({ bears: state.bears + 1 })),\n          }))\n        }\n      \u003e\n        \u003cButton /\u003e\n      \u003c/Provider\u003e\n  )\n}\n  ```\n\u003c/details\u003e\n\n## Typing your store and `combine` middleware\n\n```tsx\n// You can use `type`\ntype BearState = {\n  bears: number\n  increase: (by: number) =\u003e void\n}\n\n// Or `interface`\ninterface BearState {\n  bears: number\n  increase: (by: number) =\u003e void\n}\n\n// And it is going to work for both\nconst useStore = create\u003cBearState\u003e(set =\u003e ({\n  bears: 0,\n  increase: (by) =\u003e set(state =\u003e ({ bears: state.bears + by })),\n}))\n```\n\nOr, use `combine` and let tsc infer types. This merges two states shallowly.\n\n```tsx\nimport { combine } from 'zustand/middleware'\n\nconst useStore = create(\n  combine(\n    { bears: 0 },\n    (set) =\u003e ({ increase: (by: number) =\u003e set((state) =\u003e ({ bears: state.bears + by })) })\n  ),\n)\n```\n  \n## Best practices\n  \n* You may wonder how to organize your code for better maintenance: [Splitting the store into seperate slices](https://github.com/pmndrs/zustand/wiki/Splitting-the-store-into-separate-slices).\n  \n* Recommended usage for this unopinionated library: [Flux inspired practice](https://github.com/pmndrs/zustand/wiki/Flux-inspired-practice).\n  \n## Testing\n\nFor information regarding testing with Zustand, visit the dedicated [Wiki page](https://github.com/pmndrs/zustand/wiki/Testing).\n\n## 3rd-Party Libraries\n\nSome users may want to extends Zustand's feature set which can be done using 3rd-party libraries made by the community. For information regarding 3rd-party libraries with Zustand, visit the dedicated [Wiki page](https://github.com/pmndrs/zustand/wiki/3rd-Party-Libraries).\n\n## Comparison with other libraries\n\n- [Difference between zustand and valtio](https://github.com/pmndrs/zustand/wiki/Difference-between-zustand-and-valtio)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Faslemammad%2Fzustand","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Faslemammad%2Fzustand","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Faslemammad%2Fzustand/lists"}