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
Sails 0.10.1 cannot find module grunt #2059
Comments
@gkaimakas What steps did you take to get to this error? I can't reproduce it with a fresh install. Did you install all dependencies? |
I was using version 0.9.16 with no problems and yesterday I decided to I am using Ubuntu 14.04 both at work and home. The problem only appears at
|
@gkaimakas Did you follow the migration guide? Quite a lot of things have changed and you might have to install all dependencies again. If you're using global grunt, that should probably be updated, too. |
I fixed it by going to sails directory and installing grunt-cli. Just a 2014-08-06 9:43 GMT+03:00 Wesley Overdijk notifications@github.com:
Γιώργος |
Hoorah! Please close the issue :) |
will do! 2014-08-06 10:17 GMT+03:00 Wesley Overdijk notifications@github.com:
Γιώργος |
I think there may still be an issue here. I hypothesize that the problem lies in updating sails using npm install inside of a pre-existing sails application, when that application already has some of the sails dependencies installed via its package.json or via globally installed packages (such as grunt-cli), then npm install skips installing those dependencies that are higher up, which is fine if they are properly requested with I'm still relatively new to node and not rock-solid on package management, so I could be totally wrong, but I did notice that when I tried upgrading from v0.10.3 to v0.10.5 that all of a sudden many of the node_modules in sails were no longer there and that seems to explain the issue. The reason that I think it is a bug is because you should be able to update minor versions without causing problems, and even though this cause a fatal error break the app, it does give an annoying grunt error on lifting and more importantly screws up the asset compilation. It can be fixed by installing grunt-cli as @gkaimakas said, but sails shouldn't be looking for a file that may not be there! |
I have the same problem with sails 0.10.5. If I have grunt-cli in my package.json, npm did not install it in sails/node_modules and sails lift throw the error in module.js:340 What I did to reproduce this error ~ $ sails new myApp
~ $ cd myApp
~/myApp $ rm node_modules/ -rf
~/myApp $ npm install grunt-cli --save
~/myApp $ npm install
~/myApp $ sails lift I am using linux |
This is absolutely still an issue. I'm experiencing the same as @rmarku. |
This seems fixed in this commit and it's included in v0.11 or later. |
I created one notepad file I used the command node C:\Users\Vignesh Ravi\AppData\Roaming\npm\node_modules\sails\bin\sails.js lift and save as sails.bat file and put into C:\Windows\System32.but still I got an error while using sails lift. can anyone solve this error? Thanks in advance.... C:\Users\Vignesh Ravi\AppData\Roaming\npm\xyz>sails lift C:\Users\Vignesh Ravi\AppData\Roaming\npm\xyz>node C:\Users\Vignesh Ravi\AppData\Roaming\npm\node_modules\sails\bin\sails.js lift Error: Cannot find module 'C:\Users\Vignesh' |
Just installed sails@0.10.1 and when I lift my server I get the following error:
I saw similar problems in previous versions and every solution said to delete some backslashes from pathToSails.
the thing is that I cannot locate pathToSails anywhere. My server lifts fine though. Can anyone help ?
The text was updated successfully, but these errors were encountered: