-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
The problem with maintainability #171
Comments
I dont follow much. Utils and App folders are tightly coupled. There was never a case you need to modify just one without touching other. What good would it do to make them separate packages? Configs and lint prettier etc they hardly ever change anyway. It can be never easy to just 'upgrade' to new version, sorry I have given lot of thoughts about it and still no good trade-off. A monorepo would be way harder to maintain and keep it simple. |
I will try to share a PR by this week |
@Can-Sahin this is still WIP. https://github.com/sabarnix/react-boilerplate-cra-template/tree/wip. See if you like the idea. |
thanks will check it out. |
Ok I checked it and its pretty much what I imagined at first. But still struggling to understand how helpful would this be?
This monorepo would only come handy when doing version bumps for I like the idea actually but I feel like the components of the boilerplate is all together single unit of work. There are not really independent pieces isolated from others. I have several future plans like switching to |
After doing some more research I found that, since react-boilerplate is tied to cra, the current implementation is probably the best suited for most uses. In my case, I maintain a lot of apps created form the react-boilerplate which has some modifications like some uses rtk-query, some only redux and few uses typescript. My goal is to maintain the dotfiles for all projects in a repo and have different versions of generators. I will continue to work on the fork for my projects. I am also exploring razzle which might be better suited for my need. Will work on creating a regarding switching to |
馃檹 Thank you for this awesome React boilerplate 馃檹
Is your feature request related to a problem? Please describe.
There was a problem of maintaining (keeping track of the boilerplate changes) the project created with react-boilerplate, which was fixed to some extent by moving it to cra-template. Now, webpack and babel configs can be updated just by updating the react-script package.
For the rest of the configurations and generators, it is still difficult to update them by checking the changelog and diff.
Describe the solution you'd like
Move the project to a mono repo. Create separate packages for the generators, utils and configs (ESLINT, PREETIER etc). It will be very easy to upgrade to a new version of boilerplate this way.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: