$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>javascript - angular 8 webpack-bundle-analyzer looking for wrong polyfill files - Stack Overflow|Programmer puzzle solving
最新消息:Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)

javascript - angular 8 webpack-bundle-analyzer looking for wrong polyfill files - Stack Overflow

matteradmin11PV0评论

No matter what I do, after building my project I keep getting the following error:

Error parsing bundle asset "<path-to-project>\polyfills-es5-es2015.e1bdcd70857e70f37509.js": no such file
events.js:174

Which is exactly right seeing that my project creates a polyfills-es5.e1bdcd70857e70f37509 file and a polyfills-es2015.25bfed26497f24d6d1d7 file.

This is in a nx workspace project that I created yesterday

After every build the file names obviously changes, but it keeps looking for a mixed es5-es2015 polyfills file.

The stats file gets created as stats-es2015.json and our package.json settings is: "bundle-report": "webpack-bundle-analyzer dist/apps/<project-name>/stats-es2015.json"

I keep getting the error with default build or production, with ivy enabled or disabled, and I eve tried to remove the es5BrowserSupport flag, hoping there will only be one polyfills file, but it is still looking for es5-es2015 file...

No matter what I do, after building my project I keep getting the following error:

Error parsing bundle asset "<path-to-project>\polyfills-es5-es2015.e1bdcd70857e70f37509.js": no such file
events.js:174

Which is exactly right seeing that my project creates a polyfills-es5.e1bdcd70857e70f37509 file and a polyfills-es2015.25bfed26497f24d6d1d7 file.

This is in a nx workspace project that I created yesterday

After every build the file names obviously changes, but it keeps looking for a mixed es5-es2015 polyfills file.

The stats file gets created as stats-es2015.json and our package.json settings is: "bundle-report": "webpack-bundle-analyzer dist/apps/<project-name>/stats-es2015.json"

I keep getting the error with default build or production, with ivy enabled or disabled, and I eve tried to remove the es5BrowserSupport flag, hoping there will only be one polyfills file, but it is still looking for es5-es2015 file...

Share Improve this question edited Oct 24, 2019 at 9:37 Tony 20.2k7 gold badges41 silver badges62 bronze badges asked Oct 24, 2019 at 9:29 Alfa BravoAlfa Bravo 2,0012 gold badges29 silver badges48 bronze badges
Add a ment  | 

2 Answers 2

Reset to default 5

Try this mand to see if it work for you

ng build --prod --stats-json && webpack-bundle-analyzer dist/stats.json

My tsconfig.json

    "module": "esNext",
    "target": "es5",

I can also maybe add that I think at the end of the day my solution was just to simply close all my vsCode windows.

When ever I have vsCode open I would get the polyfills-es5-es2015.<whatever>.js": no such file error, but when I close vsCode and run the exact same mand it works...

I think it may have to do with having the angular ui plugin in vsCode, that has some kind of bundle tool as well that uses the same port as wba. So it actually has nothing to do for me with not finding the polygon file, but it still gives that error when the wba port is in use...

PS: I found this out when checking if that port was indeed in use on my machine, and it showed that it was in use by vsCode, so something in vsCode is using it and closing vsCode solved the error for me...

Post a comment

comment list (0)

  1. No comments so far