I'm using ngx-build-plus to build a standalone (angular) component like describe here: https://www.angulararchitects.io/aktuelles/your-options-for-building-angular-elements/.
Since my update to Angular 9 I've noticed a strange behaviour that wasn't happening with Angular 8:
I change something inside my standalone component and build it using ngx-build-plus. Everything works fine. Then I do a second build without having changed anything in my component and now the resulting bundle has a different content. E.g. it contains a function '_wrapNativeSuper' that the working bundle does not contain.
I tried turning off ivy for this project but that wasn't helping.
What seems to help is a 'rm -rf node'_modules/ && npm install' before each build.
command to build component:
"build:custom-element": "ng build custom-element --prod --outputHashing=none --single-bundle=true --vendor-chunk=false && ...cat files and move to specific directory...",
I'm using ngx-build-plus to build a standalone (angular) component like describe here: https://www.angulararchitects.io/aktuelles/your-options-for-building-angular-elements/. Since my update to Angular 9 I've noticed a strange behaviour that wasn't happening with Angular 8: I change something inside my standalone component and build it using ngx-build-plus. Everything works fine. Then I do a second build without having changed anything in my component and now the resulting bundle has a different content. E.g. it contains a function '_wrapNativeSuper' that the working bundle does not contain. I tried turning off ivy for this project but that wasn't helping. What seems to help is a 'rm -rf node'_modules/ && npm install' before each build.
command to build component:
"build:custom-element": "ng build custom-element --prod --outputHashing=none --single-bundle=true --vendor-chunk=false && ...cat files and move to specific directory...",
from angular.json: