-
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
ng build --profile generates empty speed-measure-plugin.json #12763
Comments
I can confirm that the speed measure file is empty on a fresh project in |
Yeah the Big |
I took a look at the files quickly and the implementation looks ok so yes it might be a problem with the webpack version, I'll try to test that this week-end if I can find some time to do it! |
Hi, any progress on that issue? It still happens in 7.1.0. Thanks. |
Issue is still reproducible on my side. Is there any workaround ? |
In certain cases the stats are not written, this seems to be because the process is being terminated before it finish to write. The reason being is using a sync version of tap. To get around this, the sync method of fs should be used to allow the creation of files. Related to: angular/angular-cli#12763
This seems to be a bug in |
…in to 1.3.1 This fixes the issue of it generating an empty speed-measure-plugin.json. Fixes #12763
…in to 1.3.1 This fixes the issue of it generating an empty `speed-measure-plugin.json`. Fixes #12763
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. |
ng build --profile
generates emptyspeed-measure-plugin.json
Command (mark with an
x
)Versions
ng --version
Repro steps
Create new project and run
ng build --profile
ng new tester-measure
cd tester-measure
ng build --profile
failure
Generated empty
speed-measure-plugin.json
Desired functionality
Not empty
speed-measure-plugin.json
additional
chrome-profiler-events.json
way to big to open in chrome. (Chrome crashes)The text was updated successfully, but these errors were encountered: