react-ketting
agile
Our great sponsors
react-ketting | agile | |
---|---|---|
3 | 19 | |
19 | 95 | |
- | - | |
0.0 | 0.0 | |
about 1 year ago | over 1 year 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.
react-ketting
-
What could be the reason why you would still chose REST over GraphQL or gRPC for your API?
I prefer REST and using HATEOAS. Its fantastic, check it out: https://restfulapi.net/hateoas/ And using tooling like https://github.com/badgateway/react-ketting and https://github.com/badgateway/ketting Makes everything extremely clean and much more simple.
- Example of a TS fetch() POST call?
- How do your handle login API, state, and errors?
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.
What are some alternatives?
Pizzly - The simplest, fastest way to integrate your app with an OAuth API
React - The library for web and native user interfaces.
ketting - The HATEOAS client for javascript
rematch - The Redux Framework
API Platform - Create REST and GraphQL APIs, scaffold Jamstack webapps, stream changes in real-time.
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.
ohm - The Openapi-HyperMedia format (OHM), is a format used to describe REST level 3 APIs.
statemanjs - Proper state manager for JavaScript
connect-go - Moved to https://github.com/connectrpc/connect-go
dawei - Lightweight state management.
jotai - 👻 Primitive and flexible state management for React
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development