-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Issue with "Sails new" originating with Forever module #567
Comments
After digging around and looking at the monitor.js file from Forever I noticed that there was a difference between their require statement and what is shown on the Utile docs... monitor.js shows
but on https://npmjs.org/package/utile they use require('util') If I change to using util it seems to make the project successfully, but I'm not sure if this breaks anything else down the line. |
Spoke too soon... wasnt paying close enough attention to notice that the docs were showing that utile is a drop in replacement for util It appears utile does infact have "inherits" so I'm puzzled as to why it says that method doesnt exist |
I'm not sure what you are trying to do. Running $ forever start app.js |
All im trying to do is run sails new.... If it doesnt use forever at all then why do i get the following when installing sails from npm
and then the ending output also includes forever
The pathing of my error even says that it is looking for forever within sails.... |
forever is also listed as a dependency on line 82 |
I uninstalled node, npm, and all modules and started from scratch. Seems to work now. |
Run into this issue if i try to do sails new...
Never experienced this in the past when running sails on my other osx box
The text was updated successfully, but these errors were encountered: