Skip to content
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

Error: ENOTEMPTY: directory not empty #66

Closed
antcook opened this issue Dec 14, 2016 · 3 comments
Closed

Error: ENOTEMPTY: directory not empty #66

antcook opened this issue Dec 14, 2016 · 3 comments
Assignees

Comments

@antcook
Copy link

antcook commented Dec 14, 2016

Using symbols (:, &, #) in nuxt.config.js stops the development server and throws an error:

I found this issue when trying to use an & in my description meta data, it only occurs when the development server is running and running yarn or npm run dev again fixes the issue and the error no longer shows.

Environment:
Nuxt 0.8.8,
Node v7.1.0

Error while rebuild the app: { Error: ENOTEMPTY: directory not empty, rmdir '/mnt/c/Users/Anthony/Documents/acook.me/.nuxt/components'
  errno: -39,
  code: 'ENOTEMPTY',
  syscall: 'rmdir',
  path: '/mnt/c/Users/Anthony/Documents/acook.me/.nuxt/components' }
This bug report is available on Nuxt.js community (#c49)
@Atinux Atinux self-assigned this Dec 14, 2016
@Atinux Atinux added this to the 1.0 milestone Dec 14, 2016
@Atinux
Copy link
Member

Atinux commented Dec 14, 2016

Hi @antcook

This error appends when the browser is calling the file while the build is not finished yet, normally it's fine and the application is still working anyway after the build is done.

It's fixed in the upcoming release.

Thank you for spotting it 👍

@Atinux
Copy link
Member

Atinux commented Dec 19, 2016

Fixed in 0.9.0

@Atinux Atinux closed this as completed Dec 19, 2016
@lock
Copy link

lock bot commented Nov 5, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 5, 2018
@danielroe danielroe added the 2.x label Jan 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants