This is a minimal example showing how iBazel doesn't keep node_modules around after a reload.
- To install:
yarn - To run broken example:
yarn start-broken - To run an example with standard reloading:
yarn start-control
- Install with
yarn - Start with
yarn start-broken - Run
ls ./dist/ibazel_webpack_example, noting that thenode_modulessymlink exists in the directory - Modify
./example_app/index.tsx, noting the errors after the reload - Run
ls ./dist/ibazel_webpack_example, noting that thenode_modulessymlink no longer exists in the directory
Multiple errors when webpack-dev-server rebuilds when running the broken example, around the lines of
ERROR in [...]/execroot/ibazel_webpack_example/node_modules/[...]
Module build failed: Error: ENOENT: no such file or directory, open '[...]/execroot/ibazel_webpack_example/node_modules/[...]'