The error I get:
DEPRECATION WARNING: Passing white, a non-string value, to unquote()
will be an error in future versions of Sass.
on line 56 of src/scss/_library.scss
events.js:85
throw er; // Unhandled 'error' event
^
Error: src\scss\_library.scss
Error: Mixin "media" does not accept a content block.
Backtrace:
src/scss/_library.scss:27, in mixin `media-above`
src/scss/_layout.scss:16
on line 27 of src/scss/_library.scss
>> #include media($min-query, null) { #content;
-----------^
This is on windows 10 with all other gulpfile configs/tools working fine. I've tried npm update, npm rebuild node-sass, npm reinstall to cheack this. The mixin is loaded before the component styles.
It works fine with ruby-sass, this error appears when I'm using the libsass complier. Any ideas on why the content block cant be accpeted in the mixin?
Related
Error while npm start in Windows 10
After npm install in vscode in my windows machine, I run npm, it starts but it shows the above error. I have cleaned cache but it did not solve.
I have searched on google but exception like this is not seen
events.js:180
throw er; // Unhandled 'error' event
^
This question is very similar to this one:
How can I fix ('throw er; // Unhandled 'error' event') code lifecycle?
For me personally, I fixed this exact issue by adding some missing environment variables to PATH.
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
I have downloaded the angular quick start code and set it up in my machine but when i run the command npm start it gives me the following errors:
Uncaught Error: Zone already loaded.
at zone.js:32
at zone.js:643
at FUNCTION (zone.js:11)
at zone.js:12
Unhandled promise rejection TypeError: Zone.assertZonePatched is not a function
at new NgZone (core.umd.js:3807)
at PlatformRef_._bootstrapModuleFactoryWithZone (core.umd.js:4524)
at eval (core.umd.js:4569)
at shim.min.js:8
at shim.min.js:8
at MutationObserver.s (shim.min.js:7)
at Zone.run (angular2-polyfills.js:138)
at MutationObserver.zoneBoundFn (angular2-polyfills.js:111)
I am using node version 6.11.3 and npm version as 3.10.10. So can anybody help me on this?
I use gulp to build my browserified files, problem is that when i have a syntax error the build fails with a generic message:
events.js:141
throw er; // Unhandled 'error' event
^ SyntaxError: Unexpected token
As you can see it's impossible to understand which file caused the error.
Is there a way to get the file name/line that caused the error?
Consider using gulp-debug https://github.com/sindresorhus/gulp-debug it is a plugin that help you see what files are run through your gulp pipeline
I need your help in the resolution of this issue, please.
The message is showing when typing the command $ionic:
$ionic ...
=========================================================================
**events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:1000:11)
at Process.ChildProcess._handle.onexit (child_process.js:791:34)**
I had the same issue due to sass setup in the project, In my case I had to change below line
"gulpStartupTasks": [
"sass",
"watch"
]
to
"gulpStartupTasks": []
in ionic.project file
https://www.bountysource.com/issues/4398734-adding-gulpstartuptasks-to-ionic-project-causes-ionic-serve-to-error-on-1-2-5
I had the exactly same problem with you.(HATE WINDOWS!)
And happily I found the solution about this, please follow the steps below:
Open C:\Users\*YOUR USERNAME*\AppData\Roaming\npm\node_modules\ionic\lib\ionic\cordova.js
Goto line 40, and
replace
var cordovaCmd = spawn('cordovaz', cmdArgs);
to
var cordovaCmd = spawn(process.platform === "win32" ? "cordova.cmd" : "cordova", cmdArgs);
try ionic run android again!
I am trying to debug a problem with forever/nodejs, and I get this stacktrace in the error log:
chdir(): Permission denied
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn EACCES
at errnoException (child_process.js:980:11)
at Process.ChildProcess._handle.onexit (child_process.js:771:34)
This looks to me like I should be able to look at line 980 of a file named "child_process.js" to see where the error is thrown. However, I cannot locate such a file on the system even with "find". Am I missing it somehow, or is the stracktrace lying?
It's part of the node.js source. See https://github.com/joyent/node/blob/master/lib/child_process.js. I believe you can also step directly through core node code using node's built-in debugger, or a package such as node-inspector.