ReactMonorepoNx Vite + Nx monorepo
To evaluate and compare the bundled and unbundled builds on large codebase.
Based on Nx and ViteJs based monorepo build toolchain.
In this project only React stack is evaluated with the goal of mixing TypeScript and Rust sources and targets.
CDN live demo
- unbundled
- bundled
- unbundled unpkg.com - unreliabe
- bundled unpkg.com
The page immediate dependencies load are meant only for bundle splitting samples.
To see the difference between unbundled and bundled distributions, within the odd or even,
click on toggle lorem tree to trigger the 3Mb of components loaded.
Quick start
yarn # will take a while as 5K source lorem files generated
yarn dev # to run in dev mode
yarn prod # run bundled production build
yarn esm # run unbundled CDN build
Directory
- HISTORY.md - the history of changes.
- apps/apps/react-monorepo-nx generated by preset app
Projects
2 main independent apps, frontend and react-monorepo-nx.
App sub-routes and ui sub-sets would include 4 big dependencies to assure the bundler would place each into separate sub-bundle.
-
front-endapp/frontendas app with 2 routes (odd,even) to loaded on demand sub-apps.- app/frontend/public/pdf 600 files from @pdftron/webviewer
-
frontend-odd/app/frontend/oddwith lazy load of PdfView and 1st Lorem tree -
frontend-even/app/frontend/evenwith lazy load of 2nd Lorem tree -
shared/sharedwith lazy load of 3rd Lorem tree
Generated files
To make the files content different, the module name and lorem ipsum generator are going to be shown by the React component.
The TS build, Eslint, IDE load time performance on large monorepo is essential, hence generating the source volume during yarn install.
The sources are generated after yarn command by postinstall script.
4,370 lorem*.ts* files, 30Mb generated in folders:
- app/odd
- app/even
- shared
To change the number of sources and file size change environment variables
-
LOREM_DEPTHfor dependency tree depth.4as default it would generate 4,370 files -
LOREM_PARAGRAPHSfor number of paragraphs in generated component file. With20the average size is about 7Kb, 30Mb total
To manual experiment change vars ^^ like export LOREM_DEPTH=2; export LOREM_PARAGRAPHS=5; yarn lorem
Build process
The yarn lorem is executed only once with the output generated excluded from git repo.
The monorepo is ready for build and run
yarn test
yarn dev # development run for frontend app
yarn build # prod build
yarn serve # run the prod build
👇generated by `react-monorepo` preset # ReactMonorepoNx
✨ This workspace has been generated by Nx, a Smart, fast and extensible build system. ✨
Start the app
To start the development server run nx serve react-monorepo-nx. Open your browser and navigate to http://localhost:4200/. Happy coding!
Generate code
If you happen to use Nx plugins, you can leverage code generators that might come with it.
Run nx list to get a list of available plugins and whether they have generators. Then run nx list <plugin-name> to see what generators are available.
Learn more about Nx generators on the docs.
Running tasks
To execute tasks with Nx use the following syntax:
nx <target> <project> <...options>
You can also run multiple targets:
nx run-many -t <target1> <target2>
..or add -p to filter specific projects
nx run-many -t <target1> <target2> -p <proj1> <proj2>
Targets can be defined in the package.json or projects.json. Learn more in the docs.
Want better Editor Integration?
Have a look at the Nx Console extensions. It provides autocomplete support, a UI for exploring and running tasks & generators, and more! Available for VSCode, IntelliJ and comes with a LSP for Vim users.
Ready to deploy?
Just run nx build demoapp to build the application. The build artifacts will be stored in the dist/ directory, ready to be deployed.
Set up CI!
Nx comes with local caching already built-in (check your nx.json). On CI you might want to go a step further.