Migration guide from react-boilerplate about react-boilerplate-cra-template

[Can-Sahin]

Unfortunately no. They are actually very different even though file patterns look similar and generalized approach for migration wouldn't work since all the projects are you know unique :)

I am also migrating to this in my projects slowly. What I am doing is:

• Creating an empty application with this template inside my project
• First carrying everything inside but the app folder, like store, locales, themes, package.json... and making sure it has minimal errors.

Up until here is not that hard. But the app folder your containers etc are totally project dependent. I am also switching to hooks so I literally go page by page.

[Can-Sahin]

"The best way" doesnt exists :( Its totally up to your 'engineering' skills I'd say. Even though this boilerplate has certain folder architecture and structure they can be bend easily. Don't force yourself to obey all the guides here. I see lot of people blindly forcing themselves to the exact same structure. Here the most beneficial part is the 'separation and isolation of functionality'. Just try to get it done right. Then it would be much simpler to implement i18n themes injected redux and saga.

So if your project is already follows the same principles I normally go feature by feature transition. I create a default boilerplate within my project and slowly transfer the features(like pages, login mechanisms, themes). Its painful and not fun at all. But much better in the long run.

[rockiger]

@Can-Sahin Could you elaborate on that? I posted a similar question on Spectrum.

For me, React-Boilerplate a kind of enlightenment and I really appreciate, that you continue development and bring react boilerplate together with CRA.

Having said that, I was wondering, what is the best way to move existing projects to react boilerplate? I think there is tremendous value in bringing homegrown project to a better structure with react boilerplate.