Gulp-sass: Update node-sass to 4.12.0 for NodeJS 12 support and to reverse a noisy CSS import deprecation warning

Created on 21 Nov 2018  路  5Comments  路  Source: dlmanning/gulp-sass

Please update node-sass to 4.11.0. That version is currently in pre-release while 4.10.0 is latest, so I expect this issue to hang around for a bit. I'll have a small PR for this shortly.

Most helpful comment

At some point in the last three months, [email protected] has been promoted from _beta_ to _latest_. @dlmanning, would you be able to review the associated PR, please? Thank you!

All 5 comments

At some point in the last three months, [email protected] has been promoted from _beta_ to _latest_. @dlmanning, would you be able to review the associated PR, please? Thank you!

I updated the associated PR with the latest version of node-sass released a few days ago that now supports NodeJS 12. @dlmanning, would be really, really great if this could be merged and released. Pretty please.

Updating node-sass to 4.12.0 does the trick as a work-around until this PR is merged.

This is not needed because of how SemVer works. You can always update the transient node-sass with npm update node-sass if you wish.

https://nodesource.com/blog/semver-tilde-and-caret

It would allow gulp-sass, amongst other changes in node-sass > 4.8.3, to finally be able to import .css files.

Currently the @import statements that contain .css file references end up in the built file as @import url ('path/to/example.css') instead of having their contents copied into the built file. I think it would be great to have this out of the box for gulp-sass.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

JamesVanWaza picture JamesVanWaza  路  4Comments

webchaz picture webchaz  路  3Comments

arontsang picture arontsang  路  5Comments

venelinn picture venelinn  路  9Comments

OskHa picture OskHa  路  7Comments