Version Information:

• NPM version (5.1.0)
• Node version (v6.9.1)
• Node Process:

{ http_parser: '2.7.0',
  node: '6.9.1',
  v8: '5.1.281.84',
  uv: '1.9.1',
  zlib: '1.2.8',
  ares: '1.10.1-DEV',
  icu: '57.1',
  modules: '48',
  openssl: '1.0.2j' }

• Node Platform (win32)
• Node architecture (x64)
• node-sass version:

node-sass       4.5.3   (Wrapper)       [JavaScript]
libsass         3.5.0.beta.2    (Sass Compiler) [C/C++]

• npm node-sass versions (npm ls node-sass):

`-- laravel-mix@0.12.1
  `-- node-sass@4.5.3

Problem Description:

I am using a third party library known as Laravel Mix to manage my webpack dependencies. I am compiling a file, known as app.scss, which has the import statement @import 'foundation' to import the Zurb Foundation library. Because the library is not immediately on my path, I’m using the node-sass feature of includePaths to add the path to the folder containing foundation.scss.

Upon running my code to compile, (by running the npm run dev script, which triggers webpack,) I reach the dependency of app.scss and then the process exits with the status of 3221225477. For the history of this error code, please see #1283. Unfortunately, I don’t think this is a duplicate, because this isn’t occurring on installation. I’d also like to add that I was unable to find a clear resolution or explanation of the problem in that thread, and would greatly appreciate someone explaining it to me in a simple manner if it’s applicable.

Error Log:

The error log created by npm is here:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\{username}\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'dev' ]
2 info using npm@5.1.0
3 info using node@v6.9.1
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle @~predev: @
6 info lifecycle @~dev: @
7 verbose lifecycle @~dev: unsafe-perm in lifecycle true
8 verbose lifecycle @~dev: PATH: {path_redacted}
9 verbose lifecycle @~dev: CWD: C:\Users\{project_path}
10 silly lifecycle @~dev: Args: [ '/d /s /c', 'npm run development' ]
11 silly lifecycle @~dev: Returned: code: 3221225477  signal: null
12 info lifecycle @~dev: Failed to exec dev script
13 verbose stack Error: @ dev: `npm run development`
13 verbose stack Exit status 3221225477
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\{username}\AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:289:16)
13 verbose stack     at emitTwo (events.js:106:13)
13 verbose stack     at EventEmitter.emit (events.js:191:7)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\{username}\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
13 verbose stack     at emitTwo (events.js:106:13)
13 verbose stack     at ChildProcess.emit (events.js:191:7)
13 verbose stack     at maybeClose (internal/child_process.js:877:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
14 verbose pkgid @
15 verbose cwd C:\Users\{project_path}
16 verbose Windows_NT 10.0.15063
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\{username}\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
18 verbose node v6.9.1
19 verbose npm  v5.1.0
20 error code ELIFECYCLE
21 error errno 3221225477
22 error @ dev: `npm run development`
22 error Exit status 3221225477
23 error Failed at the @ dev script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 3221225477, true ]

Note the command line flags on line 10, which was an effort to try and put in place something mentioned in #1283, but it also failed.