You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, @foxhound87. Thanks for nice boilerplate, but can you make light version of boilerplate in other branch? (without features, and tons pages, components, stores, utils, etc) Only with 1-2 components :)
The text was updated successfully, but these errors were encountered:
First of all this repo is a stack, afterwards can be considered a boilerplate.
I don't know what would be a light version of this stack.
Maybe you need a small MobX boilerplate without server side rendering, state hydration or others functionalities related to the utils dir? This means no need for the feathers server-side code.
Maybe some people wants to start with a minimal configuration of MobX for server side rendering (without all the advanced utils). For this purpose I will probably create a demo repo for this article. But it needs at least a minimal express and webpack setup.
To setup MobX stores without all these functionalities is pretty straightforward, and there are a lot of boilerplates doing this already.
I have a long-term plan to simplify and reduce the amount of the code externalizing the utils dir to one or more npm modules: for stores and state management, feathers utilities (hooks for ACL, automatic validation, services autoloading, etc.), bundling configurations and strategies for webpack (removing the webpack config dir if possible) and a demo package with all the custom stuff such as pages/componets/styles (so that you can get rid of them easly).
Hello, @foxhound87. Thanks for nice boilerplate, but can you make light version of boilerplate in other branch? (without features, and tons pages, components, stores, utils, etc) Only with 1-2 components :)
The text was updated successfully, but these errors were encountered: