You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, the previous version in which this bug was not present was: 11.2.14
Description
Build failes, if add deleteOutputPath: false in build options.
Seems like it might happend after update to webpack 5, cuz on angular v11 (with wepback 4) everything was fine.
ng build
√ Browser application bundle generation complete.
An unhandled exception occurred: Could not find asset for file: main.bbac280f1a66c93defc1.js
See "C:\Users\admin\AppData\Local\Temp\ng-jbrLjq\angular-errors.log" for further details.
🔬 Minimal Reproduction
Create a new project via ng new, add deleteOutputPath: false param in build options, and run ng build several times. After first build everything is fine, but if to run it again with no code changes, error occurred and build failes.
🔥 Exception or Error
√ Browser application bundle generation complete.
An unhandled exception occurred: Could not find asset for file: main.bbac280f1a66c93defc1.js
See "C:\Users\admin\AppData\Local\Temp\ng-jbrLjq\angular-errors.log" for further details.
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was: 11.2.14Description
Build failes, if add deleteOutputPath: false in build options.
Seems like it might happend after update to webpack 5, cuz on angular v11 (with wepback 4) everything was fine.
🔬 Minimal Reproduction
Create a new project via
ng new
, adddeleteOutputPath: false
param in build options, and runng build
several times. After first build everything is fine, but if to run it again with no code changes, error occurred and build failes.🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
The text was updated successfully, but these errors were encountered: