Colum Ferry

You are correct, it should be in `polyfills.ts` in the angular app, as you do not want to couple this lib with the polyfill. I will be doing some research...

Ok so I got this to work 🎉 But it's ~~kind of~~ hacky. We don't need a polyfill, rather a [ponyfill](https://ponyfill.com). The ponyfill I used was [css-vars-ponyfill](https://www.npmjs.com/package/css-vars-ponyfill). It's super quick...

The second issue has a fix merged and released in Nx 14.5.3. If you migrate to latest using `nx migrate latest` you should get it. As for the first issue,...

I believe it may have been down to an incorrect package resolution. As there is a workaround and you've got past your issue, I'll close this. Thanks for reporting!

> I believe the intent is for it to be `@ng-mf`. > > cc @Coly010 It should be `@ng-mf`. The tutorial should have been fixed to replace all `@ng-mfe` references....

Yeah, @szqsy17, if you take a look at the docs again, you'll see there are no longer any references to `@ng-mfe`

This appears to be an issue with ng-packagr (https://github.com/ng-packagr/ng-packagr). It may be worth raising the issue on their repo instead. I even tried the documentation listed on the Angular docs...

thanks for raising this. It seems there was a change to how `initialNavigation' : 'enableBlocking'` operates in Angular 14

We should make it clearer in the docs. Thanks for raising it!

You should be able to do this directly from your project.json There's an `assets` option that allows you to specify different locations for your assets. Have you tried that?