You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ng build -prod: Error: ENOTEMPTY: directory not empty, rmdir dist/vendor/rxjs/ #1409
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)
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.
Reacted by Jeff Lambert, webdeveloper0429, Sajith Shaminda, José Carlos, Shiven Sinha, Perminus Gaita, Simon M, Itheb Ben Abbes, Ivan Kalashnik, Mathis and 1 more
Reacted by Tom Iancovici, novice9888, Perminus Gaita, Simon M and Ivan Kalashnik
Activity
Headcult commentedon Jul 22, 2016
Even I'm facing the same issue. Any workaround?
filipesilva commentedon Jul 22, 2016
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 commentedon Jul 22, 2016
Removing the
distfolder manually solved the problem.filipesilva commentedon Jul 27, 2016
Closed as this issue was made obsolete by #1455.
PaulRBerg commentedon Aug 31, 2019
None of the solutions here worked for me. Using node v10.15.3 and npm 6.10.2
angular-automatic-lock-bot commentedon Oct 1, 2019
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.