Node Sass

Node.js bindings to LibSass. Lovingly maintained by @xzyfer and @nschonni 💖

[Node Sass @nodesass]

@PierB We now recommend the official sass package! Should be a drop in replacement for node-sass.

npm install sass

https://t.co/18nAk6JKrJ

[Node Sass @nodesass]

@trott @annujraval @targos89 @nodejs We do not currently have plans to ARM.

[Node Sass @nodesass]

@danielsdeboer 👀😳

[Node Sass @nodesass]

@peterbe The table identifies the minimum version required for any give Node version.

[Node Sass @nodesass]

Aloha! We're hanging out at #JSConfHI this week 🏝️ excited to see y'all

[Node Sass @nodesass]

@tastycat @xzyfer That's because we don't currently support Node arm builds. It may compile but we can't ensure it'll run correctly or not experience segfaults.

We plan to add arm support in v5, which will also drop the python 2 requirement.

[Node Sass @nodesass]

@tastycat @xzyfer We can confirm node-sass shouldn't every need to be compiled locally. If you are you must be using an version of node-sass that isn't compatible with your environment and unexpected issues may occur.

[Node Sass @nodesass]

Node 13 support has been added in Node Sass 4.13.0.

Update now for the Node 13 goodness.

[Sass @SassCSS]

CSS1 was formalized in 1996, and Sass launched in 2006. That means Sass has existed for well over half the lifetime of CSS!

[Node Sass @nodesass]

@aendrew Check out the very first line of our README to fix this problem forever.

[Node Sass @nodesass]

@usama__asfar @trott @nodejs @BethGriggs_ @BridgeAR There are Node 12 bindings in newer versions of Node Sass

[Node Sass @nodesass]

@petersuhm @parasight @thisisbranch This is not true. You should take a moment to read the very first line of our readme.

We couldn't have made it easier for you to answer your questions.

[Node Sass @nodesass]

@jamesd3142 You can avoid compiling node-sass ever again by reading the very first line of our README :)

[Node Sass @nodesass]

@__mattallan @fideloper @imadphp If you install a compatible version of node-sass for your environment you don't need the build tools. A rule of thumb is if you're building node-sass you're installing the wrong version.

Version compat is the very top of the read me: https://t.co/RKmaqOgzvH

[Node Sass @nodesass]

Say "hi" to us in Berlin at @thegraphqlconf this week

[Node Sass @nodesass]

Say "hi" to us in Berlin at @thegraphqlconf this week

[Fabriece Sumuni @sfabriece]

If you are updating to angular 8 and having troubles with SASS/SCSS:

yarn add node-sass fibers -D

That should fix your problem :)

PS: Angular-cli 8 uses dart-sass by default.

https://t.co/6TXrughaYK

#angular #angular-cli #scss #sass #webdev #angularmigration #angularv8 #ngv8

[Node Sass @nodesass]

@_JonWolfe gulp-sass has support Node 12 almost since it was released. Those PRs are redundant and will be closed. Always make sure you have the latest node-sass installed with npm update node-sass.

[Node Sass @nodesass]

@Biliology @jonasschmedtman @traversymedia @majidtarana The error message says that you're computer is unable to connect to the npm registry. Check your network and firewall settings.