Closed vdumitrache closed 3 months ago
If you use pnpm, you can set public-hoist-pattern=@angular/build in .npmrc file.
public-hoist-pattern=*@angular/build*
My guess is that pnpm and npm handle dependencies differently (yarn should be similar)
Thanks @amipei,
your comment saved us a lot of time. For the record:
@amipei Do you know why we need this?
@manfredsteyer We should keep an I on this since this is not a good DX, imho.
According to pnpm's docs, we maybe have a bug here: https://pnpm.io/npmrc#public-hoist-pattern
This setting is useful when dealing with some flawed pluggable tools that don't resolve dependencies properly.
Hi,
thanks for pointing this out. This is now resolved with version 18.1, which lands very soon.
Upgrading to the latest Angular + Native federation (18.0.2).
The error happens within an multi-project Angular Workspace, when I try to build the MFE.
Console error: _An unhandled exception occurred: Package subpath './src/builders/application' is not defined by "exports" in D:\Projects\\nodemodules\@angular\build\package.json
Full error:
Full package.json:
The angular.json builder is
"@angular-architects/native-federation:build"
calling an esbuild@angular-devkit/build-angular:application