Open rbuerschgens opened 2 months ago
It seems like this is because the package contains its own build scripts (build.js, publish.js, publish.next.js). It seems like these files are recognized as separate entry points that NF tries to compile. I need to investigate why this is the case.
We want to use in our project Fabric.js, but building the application after adding fabric as a dependency always fails with the error:
We tried adding 'fabric' to the devDependencies and also put it in the skip array of our federation.config.js. That does not change anything.
The versions we are using are: @angular/cli: 17.2.0 @angular-architects/native-federation: 17.1.6 fabric: 5.3.0
Our package.json looks like this:
And our federation.config.js like this:
What I don't understand is, that the build still tries to build the fabric library, do I miss something?