Replies: 3 comments 7 replies
-
Yup, this is because packages get bundled, so a change to a package needs to get re-bundled. The goal of Snowpack was to isolate all bundling costs to the install step (runs once, on install) since that happens much less than server startup or on change. Monorepos should be able to take advantage of a faster workflow (since you as the author can guarantee that they are ESM). It would be interesting to experiment with aliases to linked dependencies. If you alias |
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply and explanation.
Does not unfortunately. When doing this, it seems that it then tries to bundle all dev dependencies of packages (some of which don't run in the browser, since I'm developing for both node and browser) since node_modules is now hoisted. Unless I am misunderstanding what you mean? |
Beta Was this translation helpful? Give feedback.
-
#2707 includes a ton of updates for monorepos, including this support. Would love your feedback if you can check out that PR (npm install snowpack@next) |
Beta Was this translation helpful? Give feedback.
-
When using Lerna & Yarn workspaces, Snowpack running in a non-package folder requires the cache to be reloaded for any changes in the package source to take effect.
Running on Ubuntu 18.04.5 LTS
[email protected]
[email protected]
[email protected]
Beta Was this translation helpful? Give feedback.
All reactions