appleboy / appleboy/gulp-compass
compass.rb on project directory
- Dominant language
- JavaScript
- Stars
- 172
- Forks
- 54
- PR merge metrics
- No merged PRs in 30d
Description
I have a simple project with some scss files, I was using compass without config.rb to compile it to css.
But than I diceded to use one config.rb and I have named it compass.rb; and then the nightmare started.
I have reinstalled node, redownload all the dependencies nothing worked. In nutshel the misterious error:
``` internal/child_process.js:298
throw errnoException(err, 'spawn');
^
Error: spawn UNKNOWN
at exports._errnoException (util.js:873:11)
at ChildProcess.spawn (internal/child_process.js:298:11)
at exports.spawn (child_process.js:362:9)
at module.exports (\node_modules\gulp-compass\lib\compass.js:149:15)
at DestroyableTransform.compile [as _flush] (\node_modules\gulp-compass\lib\index.js:60:5)
at DestroyableTransform. (\node_modules\gulp-compass\node_modules\through2\node_modules\readable-stream\lib\_stream_transform.js:135:12)
at DestroyableTransform.g (events.js:260:16)
at emitNone (events.js:72:20)
at DestroyableTransform.emit (events.js:166:7)
at finishMaybe (\node_modules\gulp-compass\node_modules\through2\node_modules\readable-stream\lib\_stream_writable.js:3
71:12)
```
was caused by naming composer configuration file to compass.rb. After renaming it to something else like compassconfig.rb everything worked flawlesly.
I do not know it is a bug but is should be documented somewhere that you can not name your gulp-composer configuration file to composer.rb because it will fail to run.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the failure with a project configuration named compass.rb, then compare it with compassconfig.rb. Start by reading node_modules/gulp-compass/lib/compass.js and lib/index.js at the stack-trace locations. Done means confirming the filename conflict and either documenting the restriction or defining a verified fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100