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

Development server crashes if nuxt.config.js becomes invalid #60

Closed
soutokevin opened this issue Dec 11, 2016 · 3 comments
Closed

Development server crashes if nuxt.config.js becomes invalid #60

soutokevin opened this issue Dec 11, 2016 · 3 comments
Assignees

Comments

@soutokevin
Copy link

soutokevin commented Dec 11, 2016

If the configuration file change during the execution of the development server, it automatically aplies the new configuration, but if the file becomes invalid (a missing comma or semicolon, we all do that sometimes!) the server crashes, needing to be restarted (after fixing the file).

When running a development server, I don't expect it to crash for any reason, no matter what happens the server should only display an error message and wait until things go back normal.

This feature request is available on Nuxt.js community (#c44)
@Atinux Atinux added this to the 1.0 milestone Dec 11, 2016
@Atinux Atinux self-assigned this Dec 11, 2016
@Atinux
Copy link
Member

Atinux commented Dec 12, 2016

Thank you @soutokevin

It will be fixed in the new release.

@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