-
Notifications
You must be signed in to change notification settings - Fork 37
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
Cannot GET /
after Vagrant initialization
#14
Comments
I think it might be related to this issue: npm/npm#9633 (comment) If it's not related directly, there at least seems to be some sort of race condition in the background that screws up the node modules based on it sometimes working & sometimes not. |
@paulbert think |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some people have experienced an error after initializing their virtual machine. It appears to only happen on occasion and has occurred on OSX and Windows, so the cause is unclear at this time.
The text was updated successfully, but these errors were encountered: