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
Dependencies installed can be different than what is in donejs-cli #590
Comments
Hey @tracer99, in the folder where you are initing from, do you have a |
I once found an error because the parent folder had a |
I ran init in my home dir. I don't have a node_modules dir there. |
@tracer99 Did the folder have a package.json by any chance? |
Nope. |
I re-did an init on a clean install (not into an existing dir)
This is the package.json that was generated https://gist.github.com/tracer99/85d10956dc20a170fa55 |
Anything in the existing directory at all? |
We have a boilerplate new git project init on our git server. This is what it creates and what the dir had:
|
So you can see in that package.json that |
Ok, I was able to reproduce this issue. Prior to 0.9, this issue could occur if you had a package.json in any parent directory of where you're initializing a new app.
|
This was reported in gitter:
https://gitter.im/donejs/donejs?at=56f44b78d39de41b495d87b2
What's interesting is that most of the package.json is up-to-date, it's just the dependency list that is not.
The text was updated successfully, but these errors were encountered: