![]() ![]() As long as you are prepared for the possibility of ‘ejecting’ in the future and extending/simplifying your build process manually, go for it. It is really magical to create a transpiled, compressed, ‘tree-shaken’ production bundle in a single command line. Having said that, create-react-app is great for POCs or quickly churning out a React SPA. It will slowly grow into a big legacy app with feature after feature tacked on without regard for ‘spaghetti-ness’, bloat, performance and latency. Can you reason your build process easily in a TOI session? If not, the app you built so hard will not evolve. Let’s have some empathy for the ones that succeeds you. You will move on to other projects/companies at some point. This applies to a typical create-react-app application in other use cases. How isolated is the usage? How much bloat will this new library add to the production code? The best way to consume React-Bootstrap is via the npm package which you can. Research and team-review every npm module before you add them. (babel, css preprocessors, routing, i10n, hot reloading, TDD workflow, lodash/ramda/moment etc.) As you start developing features you you will need extra third party libraries/packages. Start with a basic build environment with webpack. ![]() Trimming your build after an eject may be a daunting task.įor production apps that will grow, I will not recommend going the create-react-app route. create-react-app is a generic framework that need to account for several scenarios. Create React App assumes your application is hosted at the serving web server's root or a subpath as specified in package.json (homepage). create-react-app uses this name to make a new directory, then creates the necessary files inside it. Trimming your build after an eject may be a daunting task. create-react-app takes one argument: the name youd like to give your app. At this point you are faced with hundreds of npm modules that you have little clue about. create-react-app is a generic framework that need to account for several scenarios. Sooner or later, your app will grow and you will need to do the dreaded ‘eject’. But in real life, your application will not stay within the proposed limits of the create-react-app framework. If all you need is to get your feet wet in React or create a small SPA, this would do. The problem with adopting create-react-app for production
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |