-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can't seem to get SourceMaps to turn off #57
Comments
Why setting Plus, Pleeease already includes Sass, you don't need There's an example with Stylus from |
Ok. I'll try that. I had sourcemaps set to false to because I was using gulp-sourcemaps and I wanted and external sourcemap. However, Pleeease was inlining it even when set to false. I'll give it a go using all of Pleease's configs. Thanks! |
Yeah, I can't get it to work. adding:
leads to this error
if I clear out the source file completely I then get this error:
Totally confused about this right now. |
The solution provided above isn't working for me. When using Pleeease for Sass (indented syntax)
I get more errors. I don't think that it's picking up the indented syntax configuration
When I clear out the sass file used as the source, I then get this error:
Totally confused right now. Also, I'm using ES6 on my gulpfile. Not sure if that matters in this case, but figure I should tell you. |
Also, I found the issue with the sourcemaps not turning off. Even with sourcemaps turned to false in pleaseOptions, piping
Thus, even if I don't want to use Pleeease for sourcemaps, I still get it anyway. In the usage above, I actually get two source maps. I get an inlined one from Pleease and reference to an external one via I am using sourcemaps separately from Pleeease because I'm using it for my Sass and JS externally.Both of my Sass and JS tasks are writing external sourcemaps to a |
Versions:
"gulp-pleeease": "^1.2.0",
"gulp-sass": "^2.0.4",
"gulp-sourcemaps": "^1.5.2"
Am I missing something here?
Thanks for Pleeease! I'm a huge fan! Stay awesome!
The text was updated successfully, but these errors were encountered: