Skip to content

ng build -prod: Error: ENOTEMPTY: directory not empty, rmdir dist/vendor/rxjs/ #1409

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

Closed
WG-Com opened this issue Jul 21, 2016 · 6 comments
Closed

Comments

@WG-Com
Copy link

WG-Com commented Jul 21, 2016

ng build -prod
(node:7057) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
Built project successfully. Stored in "dist/".
File sizes:
fs.js:95
      throw err;  // Forgot a callback but don't know where? Use NODE_DEBUG=fs
      ^
Error: ENOTEMPTY: directory not empty, rmdir dist/vendor/rxjs/'  at Error (native)
@Headcult
Copy link

Even I'm facing the same issue. Any workaround?

@filipesilva
Copy link
Contributor

That error is usually due to the dir being open somewhere. Common culprits are ng serve, the editor you're using (VSCode for instance), or having the folder open in explorer. Try closing all of those.

@rgajam
Copy link

rgajam commented Jul 22, 2016

Removing the dist folder manually solved the problem.

@filipesilva
Copy link
Contributor

Closed as this issue was made obsolete by #1455.

@PaulRBerg
Copy link

None of the solutions here worked for me. Using node v10.15.3 and npm 6.10.2

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants