Nice writeup. My experience with npm link has been mostly negative, especially when you have to work on multiple dependencies and app.
I’ve written a tool that’s a fully functional package manager and focus on having a super easy and powerful npm link feature. https://www.npmjs.com/package/fyn
I hope you will give it a try.
Hi Tomas, thanks for clarifying. We are evaluating npm ci for our builds. As far as I can tell, having package-lock.json does cut down the install time significantly already. It’d be interesting to see what the overhead of the checking and resolution are and how that can be optimized and cut down further, so our daily regular npm install will also…
If package-lock.json exist, then npm install should’ve honored it and use versions from there instead of doing full meta fetching and resolution. How is that different from npm ci in terms of performance? It seems the only difference in npm ci is that it fails if package.json was updated without updating package-lock.json.
electrode-redux-router-engine now supports a
init attribute in your route to define a custom store initializer. https://electrode.gitbooks.io/electrode/content/chapter1/advanced/stand-alone-modules/redux-router-engine.html#init-attribute
That’s definitely something to look into. It would depend on some plugin to do dead code removal and then tree shaking to remove unref modules. I am not sure how feasible that is yet.