Default to watching dependencing in development?

Assume a monorepo setup, where many addons are linked by default:

• a person launches an app via ember s
• but then decides they want to edit an addon (and rebuild it // rollup -c --watch)
• when the v2 addon re-outputs its artifacts, the host app should detect that

Reasoning:

• until we get to a dev-time environment as efficient as Vite, the initial startup time for apps can be costly (though, I’ve yet to experience what a large app is like with all v2 addons — I’ll know more on this in the coming months though)

[lifeart]

Ya, I don’t like idea where ember-cli is watching for every item in node_modules.

Some possible optimizations:

• create watched tree only for specified deps
• autodetect watched deps (if it’s symlink or package.json has “file:” reference to it)
• if it’s not ember-addon, likely we don’t need to watch it by default

I would say that development in node_modules it’s likely 1% of usual day-to day actions for FE developers, and likely we should not spend resources of 99% devs to support 1% by default

[NullVoxPopuli]

deps could have nested node_modules, and may be not a case

I’m proposing to ignore those. To only watch what is specified in an app’s `package.json#dependencies

• only if :
  • they are within the same repo
  • or if they are linked (like your suggestion says 🥳 )

one dev-dep could lead us to bunch of side watched folders inside node_modules/{dep}/node_modules/{…}

If we only watch the shallow dependencies-of-the-app’s output folder (dist in most cases), then none of nested ‘node_modules’ would matter