nextjs-redux-observable
ducks-modular-redux
nextjs-redux-observable | ducks-modular-redux | |
---|---|---|
1 | 17 | |
0 | 9,587 | |
- | - | |
10.0 | 0.0 | |
over 1 year ago | over 2 years ago | |
JavaScript | JavaScript | |
- | - |
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.
nextjs-redux-observable
-
How to Build a Basic CRUD App with NextJS, React, Redux, Observable and MUI5 Components
As always, the complete source code is available on GitHub: https://github.com/czetsuya/nextjs-redux-observable.
ducks-modular-redux
-
What are some good ways to structure React projects and separate logic from every component? Design patterns and code/folder structure
And here's an interesting proposal for organizing data store/reducer logic: https://github.com/erikras/ducks-modular-redux
- How to Build a Basic CRUD App with NextJS, React, Redux, Observable and MUI5 Components
- How to Build a Basic CRUD App with NextJS, TS, React, Redux-Tookit and MUI5 Components
- Redux explicado de manera simple y sucinta para los desarrolladores de React
- Introducción react-redux y redux toolkit
- Introduccióna react-redux y redux toolkit
-
Should we be teaching Redux in 2022?
Yeah, the "ducks" file structure has been around as an idea since 2015, but most Redux apps (and our older docs) used a "folder-by-type" pattern (/reducers/todos.js, /actions/todos.js, etc).
-
Day 30 of #100daysofcode: Re-ducks and Best Practices
The official Redux Style Guide suggests using the (very modular) Ducks structure. Essentially, this structure follows the design pattern of "New Feature? New folder." I am not 100% sure, but this seems to be a newer development in Redux best practices. For example, favesound-redux splits files into "type" folders.
-
React folder structure for enterprise level applications
That's an idea that has been around for awhile and was popularized by the Duck pattern for Redux.
-
Stepping up your Redux game with Redux Toolkit
The original Redux docs examples did show a "file-by-type" folder structure (ie, /actions/todos.js, /reducers/todos.js, etc), but you've always been able to structure your code however you want to. The "ducks" pattern was invented right after Redux came out, and has always been a valid approach.
What are some alternatives?
react-redux-firebase - Redux bindings for Firebase. Includes React Hooks and Higher Order Components.
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
nextjs-redux-toolkit - NextJS Typescript Integration with Redux Toolkit
redux-devtools - DevTools for Redux with hot reloading, action replay, and customizable UI
unsplashapp - React Native app for browsing https://unsplash.com/
react-community-tools-practices-cheatsheet - Descriptions and use cases for common tools and practices in the React community
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
react-redux - Official React bindings for Redux
SAAS-Starter-Kit-Pro - 🚀A boilerplate for building Software-as-Service (SAAS) apps with Reactjs, and Nodejs
flux-standard-action - A human-friendly standard for Flux action objects.
lab-next-ts - NextJS Typescript Integration with Redux Toolkit [Moved to: https://github.com/czetsuya/nextjs-redux-toolkit]