NPM error: Sails.js crashes after restarting my pc #4501

emmsdan · 2018-09-01T02:24:37Z

Sails version: 0. 12. 14
Node version: v8. 11. 4
NPM version: 6. 4. 1
DB adapter name: N/A
DB adapter version: N/A
Operating system: window 7

BEGIN PLEDGE

I am experiencing a concrete technical issue (aka a bug) with Sails (ideas and feature proposals should follow the guide for proposing features and enhancements (http://bit.ly/sails-feature-guide), which involves making a pull request). If you're not 100% certain whether it's a bug or not, that's okay--you may continue. The worst that can happen is that the issue will be closed and we'll point you in the right direction.
I am not asking a question about how to use Sails or about whether or not Sails has a certain feature (please refer to the documentation(http://sailsjs.com), or post on http://stackoverflow.com, our Google Group (http://bit.ly/sails-google-group) or our live chat (https://gitter.im/balderdashy/sails).
I have already searched for related issues, and found none open (if you found a related closed issue, please link to it in your post).
My issue title is concise, on-topic and polite ("jst.js being removed from layout.ejs on lift" is good; "templates dont work" or "why is sails dumb" are not so good).
I have tried all the following (if relevant) and my issue remains:
- Make sure you have the right app lifted.
- Make sure you've killed the Sails server with CTRL+C and started it again.
- Make sure you closed any open browser tabs pointed at localhost before starting Sails.
- Make sure you do not have any other Sails apps running in other terminal windows.
- Make sure the app you are using to reproduce the issue has a clean node_modules/ directory, meaning:
  - no dependencies are linked (e.g. you haven't run npm link foo)
  - that you haven't made any inline changes to files in the node_modules/ folder
  - that you don't have any weird global dependency loops. The easiest way to double-check any of the above, if you aren't sure, is to run: rm -rf node_modules && npm cache clear && npm install.

and finally...

I can provide steps to reproduce this issue that others can follow.

I am new when it comes to using sail.js.

I installed Sail.js and then using sails lift I started the app it went well.

after sometime, I switched of my laptop, just to turn it on back I then an error.
It won't start.

I created a new project in another folder it worked well.
I switched off my laptop and switched it on again, and i get the same error.

Please What is really happening.

here is the error

C:\emmsdan\main\mws-looper-two\node_modules\machine\lib\Machine.prototype.exec.js:1(function (exports, require, module, __filename, __dirname) { MZP


SyntaxError: Invalid or unexpected token
at createScript (vm.js:80:10)
at Object.runInThisContext (vm.js:139:10)
at Module._compile (module.js:616:28)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (C:\emmsdan\main\mws-looper-two\node_modules\machine\lib\Machine.constructor.js:149:26)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (C:\emmsdan\main\mws-looper-two\node_modules\machine\index.js:1:80)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)

The text was updated successfully, but these errors were encountered:

sailsbot · 2018-09-01T02:24:53Z

Hi @emmsdan! It looks like you missed a step or two when you created your issue. Please edit your comment (use the pencil icon at the top-right corner of the comment box) and fix the following:

Verify "I am experiencing a concrete technical issue (aka a bug) with Sails (ideas and feature proposals should follow the guide for proposing features and enhancements (http://bit.ly/sails-feature-guide), which involves making a pull request). If you're not 100% certain whether it's a bug or not, that's okay--you may continue. The worst that can happen is that the issue will be closed and we'll point you in the right direction."
Verify "I am not asking a question about how to use Sails or about whether or not Sails has a certain feature (please refer to the documentation(http://sailsjs.com), or post on http://stackoverflow.com, our Google Group (http://bit.ly/sails-google-group) or our live chat (https://gitter.im/balderdashy/sails)."
Verify "I have already searched for related issues, and found none open (if you found a related closed issue, please link to it in your post)."
Verify "My issue title is concise, on-topic and polite ("jst.js being removed from layout.ejs on lift" is good; "templates dont work" or "why is sails dumb" are not so good)."
Verify "I have tried all the following (if relevant) and my issue remains:"
Verify "I can provide steps to reproduce this issue that others can follow."

As soon as those items are rectified, post a new comment (e.g. “Ok, fixed!”) below and we'll take a look. Thanks!