-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watch mode of @angular-devkit/build-angular:browser
is broken
#21038
Comments
Note: it’s unlikely that you want to run To run watch mode on development builds you can run.
|
…re present on rebuilds Webpack will only provide emitted assets in the returned Stats each rebuild unless the `cachedAssets` option is enabled. This is currently needed for the bundle budget calculations. Fixes angular#21038
…re present on rebuilds Webpack will only provide emitted assets in the returned Stats each rebuild unless the `cachedAssets` option is enabled. This is currently needed for the bundle budget calculations. Fixes #21038
In general of course not. However, I'm testing loading times for my SSR enabled pages with this command, which gave the same error:
I use Argo tunnel to open the page on a real mobile device and/or lighthouse in the browser. @alan-agius4 Just wanted to mention this in case it's not covered by the above fix, but I'm guessing it probably would be. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
🐞 Bug report
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was: v11.xDescription
When running an
@angular-devkit/build-angular:browser
target with--watch=true
, the builder eventually fails with the message:An unhandled exception occurred: Could not find asset for file: main.cc7ab080d48901fb3cbd.js
.Running the command again then works until a file is changed. Then it crashes again.
🔬 Minimal Reproduction
The last command crashes.
Running it again works.
Now change a file, like
app.component.html
, it will crash again.🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
I have the same result on two different MacOS machines.
The text was updated successfully, but these errors were encountered: