Updating to New (Future) Releases

[superKalo]

Hello @bharani91 ,

I was wondering what are the guidelines (the best practice approaches) to adopt (use) the boilerplate, in order to get future changes/updates/releases? Obviously, I can just clone the repo and start doing changes on top, but that doesn't sound to me very maintainable... Or is it? 👷

I'll appreciate if you please share your thoughts.

PS: Thanks for sharing your awesome work! ⭐️ I appreciate it a lot! 🤘

[bharani91]

Hi @superKalo,

Glad that you find this project useful.

To be honest, I am not quite sure about it myself. The codebase for my original extensions (from which I extracted this project) has diverged quite a bit from this.

I have been thinking of a way to abstract this into a module that can be imported and used as a base. This will allow for easier updates & better maintainability.

I will update this issue when I make some progress. In the meantime, I am open to suggestions.

[superKalo]

Thanks for your reply!

I have been thinking too, and I think the way react-create-app did it does worth checking.

Long story short - they configured it as a one dependency It uses Webpack, Babel, ESLint, and other tools internally, but it provides an 'API for communication' on top of them. Something similar may serve as an abstraction layer, which could be easily maintained while the 'API for communication' in the middle doesn't introduce breaking changes.

However, this might be a bit tricky for implementation. In case I have any other idea - I will write to you. Anyways, I truly hope I see newer releases in the near future 👍