agile
redux
Our great sponsors
agile | redux | |
---|---|---|
19 | 268 | |
95 | 60,454 | |
- | 0.3% | |
0.0 | 9.0 | |
over 1 year ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
agile
-
"You may need an additional loader to handle the result of these loaders."
If you want to know more checkout this repo:https://github.com/agile-ts/agile
-
Pass parent config object directly into child method (requires not all properties) or redefine it ๐ค
I was wondering about this weird question as I'm trying to build a fast State-Management framework. And currently, I'm micro optimizing it to make it as fast as possible.
-
React and Redux Toolkit Full Course (free) ๐ฅ - Complete Shopping Cart Project
I faced the same issue, and so I created a State Management library (AgileTs) based on the neat atom concept of Recoil. AgileTs isn't bound to React, and therefore the global States can be modified and accessed outside the React tree.
-
createState("Introducing AgileTs. A flexible State-Manager");
Doucmentation
This allows you to preview and edit your global bound States at runtime. For example, the core of the AgileTs documentation is globally bound for better debugging. Note that you should avoid attaching your application States to the globalThis in production because then third parties can easily interfere in your internal application logic. Since the AgileTs documentation has no vulnerable logic under the hood, the core is also accessible in production. Thus you can play around with the AgileTs documentation core and, for example, update the NPM_DOWNLOADS State or update the astronaut color.
-
What's your favorite state manager?
It might sound self-indulgent, but my favorite State Manager is, of course, the one I've created myself called AgileTs. It's a singleton-based State Manager, which means your States are singletons, and are not tied to a single source of truth store object. This gives you much more flexibility in structuring your store the way you need it. Here are some Style Guides on how you might structure your application using such a singleton State Management approach \^)
- State Management made easy. AgileTs is a global, simple, spacy State and Logic Framework for JavaScript applications.
- How does the unpacked size affect the minified size of an npm package?
-
https://np.reddit.com/r/reactjs/comments/m0hk63/do_you_use_vanilla_react/gqant0j/
Well.. AgileTs is a simple state manager that is supposed to be an alternative to redux, mobx and zustand..
-
Do you use `vanilla React`?
Well.. that depends on the project.. (In my opinion) There is often no need for external dependencies on small projects like a single-page application, apart from nextjs, (since I want good performance). If it's a more significant project with more advanced logic, I always have a State Management Framework like AgileTs in action because passing states through multiple components is annoying. Regarding UI components, I try to build my own components as much as possible and only use external components if these correspond precisely to my needs. For instance, toastify is often an external dependency in my projects.
redux
-
A Comprehensive Guide to React State Management
Redux
-
Full Stack Web Development Concept map
redux - Redux is a key tool used in managing state across an application. This can be used with any web technology including React, Vue and Angular docs
-
State Management Nx React Native/Expo Apps with TanStack Query and Redux
Redux is a client-state library.
- Redux 101
-
The 20 most used React libraries
react-redux: A powerhouse for efficient state management and data flow control. Learn more
-
React State Management in 2024
Reducer-based: requires dispatching actions to update a big centralised state, often called a โsingle source of truthโ. In this group, we have Redux and Zustand.
- Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes (plus major versions for all Redux family packages!)
-
Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes, and more
I am _thrilled_ to announce that:
Redux Toolkit 2.0 is LIVE!!!
- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0
This major version has new features, faster perf, smaller bundle size, and removes deprecated options.
It's accompanied by majors for all our Redux family packages
## RTK 2.0:
- a new `combineSlices` method for lazy-loading reducers - Updates to `createSlice` to include a `selectors` field and allow defining thunks inside
- Immer 10 w/ faster updates
- Removal of deprecated options
See the migration guide:
- https://redux.js.org/usage/migrations/migrating-rtk-2
All of the Redux libraries now have modernized packaging with full ESM/CJS compat. They also ship modern JS (no transpiling for IE11), which means smaller bundle sizes.
We've also done byte-shaving work to shrink the bundles (extracting error messages, de-duping imports)
## Redux core 5.0:
- The TS conversion we did in 2019!
- Action types _must_ be strings
- `UnknownAction` as the default action type
- Better preloaded state types
- Internal subscription improvements
- Still marks `createStore` as deprecated!
- https://github.com/reduxjs/redux/releases/tag/v5.0.0
## React-Redux 9.0:
- *Now requires React 18 and RTK 2.0 / Redux 5.0*
-
HTML Data Attributes: One of the Original State Management Libraries
DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.
-
Blogged Answers: My Experience Modernizing Packages to ESM
Oh hey, that's my post!
(yes I spend too much time refreshing HN :) )
FWIW I did end up with a packaging combination that seems to work sufficiently. I never did fix the "FalseCJS" issue that `are-the-types-wrong` is detecting. I played with double-emitting TS typedefs, and the `tsup` tool _does_ actually have support for that now (added by Andrew Branch from the TS team). So it might be more feasible now. But ultimately I decided I was tired of messing with packaging setup and that what I've got is good enough. (hopefully)
We're actually about to launch Redux Toolkit 2.0 and Redux 5.0 this week, assuming the last couple pieces come together. Here's the latest RCs - you can see the current `package.json` files in there:
- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0...
- https://github.com/reduxjs/redux/releases/tag/v5.0.0-rc.1
What are some alternatives?
React - The library for web and native user interfaces.
zustand - ๐ป Bear necessities for state management in React
rematch - The Redux Framework
remix - Build Better Websites. Create modern, resilient user experiences with web fundamentals.
react-ketting - Ketting bindings for React
SWR - React Hooks for Data Fetching
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
valtio - ๐ Valtio makes proxy-state simple for React and Vanilla
statemanjs - Proper state manager for JavaScript
swift-composable-architecture - A library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind.
dawei - Lightweight state management.
react-query - ๐ค Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]