Closed OleVik closed 8 years ago
Where is the origin of this error? Could you please provide a full stack trace?
I'm not quite sure how to obtain a full stack trace, would the equivalent from gulp-plumber
work? Here is the output from its errorHandler (slightly formatted for readability):
{ [TypeError: Bad argument]
name: 'TypeError',
message: 'Bad argument',
stack: 'TypeError: Bad argument
at TypeError (native)
at ChildProcess.spawn (internal/child_process.js:274:26)
at Object.exports.spawn (child_process.js:362:9)
at node_modules\\phridge\\lib\\spawn.js:103:38
at init (node_modules\\when\\lib\\makePromise.js:39:5)
at new Promise (node_modules\\when\\lib\\makePromise.js:27:53)
at Function.promise (node_modules\\when\\when.js:97:10)
at startPhantom (node_modules\\phridge\\lib\\spawn.js:73:25)
at tryCatchReject (node_modules\\when\\lib\\makePromise.js:845:30)
at runContinuation1 (node_modules\\when\\lib\\makePromise.js:804:4)
at Fulfilled.when (node_modules\\when\\lib\\makePromise.js:592:4)\n
at Pending.run (node_modules\\when\\lib\\makePromise.js:483:13)
at Scheduler._drain (node_modules\\when\\lib\\Scheduler.js:62:19)
at Scheduler.drain (node_modules\\when\\lib\\Scheduler.js:27:9)
at nextTickCallbackWith0Args (node.js:452:9)
at process._tickCallback (node.js:381:13)',
showStack: false,
showProperties: true,
plugin: 'gulp-uncss' }
Okay. Looks like this is a duplicate of this bug; https://github.com/giakki/uncss/issues/75
I get an error saying:
With a fairly typical setup:
However, running through the UnCSS CLI it progresses as expected. This is with
gulp-uncss@1.0.5
anduncss@0.13.0
. Thehtml
-option seems correct enough, what could be causing the error?