NPM workspaces support when bundling with @nx/webpack:webpack

[dar-yl]

By default, the @nx/webpack:webpack executor treats NPM workspace libs as external dependencies (does not bundle them). This causes a big problem when related packages are private..

#10386 provides a summary of the issue / workarounds (note: I attempted the workaround suggested by the OP, however, it did not work). I believe the workarounds are:

1. remove affected libs from npm workspaces array
2. maintain a list of externalDependencies in the NxAppWebpackPlugin

Neither of these workarounds are viable solutions as they create additional problems (I hope these are obvious without an explanation).

I suggest extending NxAppWebpackPlugin:

1. Automatically bundle libs that form part of the Nx workspace - yes, there are side effects to this, however, I believe this is still an improvement to the situation.
2. To handle the above, provide a bundleInternals to control the above. Either a bool, or options list, e.g. 'all' | 'none' | 'private'

I'm unsure of the behaviour in yarn / pnpm. If I can get some feedback, I'd be more than happy to submit a PR for this.