-
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
Permission error on second build when nomodule polyfill is included #15490
Comments
Some other users also seem to experience |
According to the other issue, this may happen even without the change to browserslist. I thought the problem popped up when I made that change, but I could easily have missed that. |
Yeah, the issue is not related to the browserslist file per see, it's related to a change in 8.3. |
I had the same problem and after removing node_modules and |
I get this error:
The problem is fixed by PR #15512, but many of the generated files are now world-writable (see below). Deploying these files could be less secure than before. I know nothing about the internal workings of an angular build, but it looks like files are cached and later copied to 'dist'. The files in the cache already have their mode reset to 0o444. Wouldn't it be possible to save the file there with the correct permissions? If not I would advocate for a less open mode of 0o664 or 0o644. Nonetheless, thank you for looking into this issue.
|
@chtisgit Assets being processed as described in that error was a bug that was fixed in the 8.3.1. Please ensure that the CLI is at the latest version (8.3.2) and the As to the permissions, does the project have the |
…dles copyFilesSync will also copy permissions which may result in permissions errors. Closes #15490
…dles copyFilesSync will also copy permissions which may result in permissions errors. Closes #15490
Can someone help me on this, I am getting this error 'EEXIST: file already exists, mkdir' I have:
|
Same problem with:
|
In my case I just added the |
This not works for me, do you do any other thing? |
@pagimaxx I had the same issue, but it was resolved after running |
I'm not entirely sure how this aids the Just sounds like a coincidence to me. |
@jjz4689 my assumption is that some data in the npm cache was causing the issue. Worked for me 🙃 |
@JoeOsterfeld Ah yes, makes sense - maybe the devkit for build was getting cached, hence the failure even after updating in package.json 🤔 EDIT: |
Im still having this issue with SSR.
works once, but when you do another:
Im still getting
|
@borriej I don't think running In my case, I just swapped out my But, I can't be totally sure if this is what's causing the issue for you, and in my case, I'm not running SSR. |
im having this on my local machine using
even running a single
gives the error
caused by Differential Loading :(, because the error comes after
browserlist is empty and tsconfig looks like
|
I'm no expert, but I'd suggest, if you are still having this problem with the latest Angular CLI, completely deleting node_modules, and re-installing. Then, if you are still having the problem, report this as a new related issue (with a link to this one), since this issue is closed, and was fixed, at least for the case reported originally. |
If anyone is encountering the EEXIST error on MacOS, please try a node version of 10.16.0 or greater. There is a known issue with copying files on earlier versions of node for MacOS. |
wow thanks guys! I solved it... I was using solution was to use the stable Node!
|
I was getting the same issue running "npm run electron-build" which of course does an "ng build --prod". I was using node 11.6.0. I installed n from npm and got node 10.16.3, 11.15.0 and 12.10.0... When I used node version 10x or 12x everything was fine, but with node version 11x the problem just will not go away. https://www.surrealcms.com/blog/how-to-upgrade-or-downgrade-nodejs-using-npm.html |
this helped me as well - deleting and re-installing node_modules |
Apparently, error mentioned a |
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?
I'm not sure. This is the first time I've seen it, but I recently upgraded to Angular 8.
Description
I reproducibly get a permission error, seen below, in a clean, brand new angular project, when browserslist specifies browsers that require nomodule polyfill.
🔬 Minimal Reproduction
ng new test
ios_saf >= 10
ng build --prod
ng build --prod
(again)🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
Nuking
node_module
(and presumably just the cache dir within) and reinstalling fixes the issue for one build.Sorry to put this out there on a Friday afternoon!
The text was updated successfully, but these errors were encountered: