Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

node-sass@1.2.3 postinstall failing on Ubuntu 12.04.5 #550

Closed
ixtli opened this issue Nov 20, 2014 · 38 comments
Closed

node-sass@1.2.3 postinstall failing on Ubuntu 12.04.5 #550

ixtli opened this issue Nov 20, 2014 · 38 comments

Comments

@ixtli
Copy link

ixtli commented Nov 20, 2014

The following is the relevant section of the failure:

jenkins@jenkins:XXX$ npm install node-sass
|
> node-sass@1.2.3 install XXX/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at XXX/node_modules/node-sass/vendor/linux-x64/binding.node

> node-sass@1.2.3 postinstall XXX/node_modules/node-sass
> node scripts/build.js

`linux-x64` exists; testing
module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (XXX/node_modules/node-sass/lib/index.js:181:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)

npm ERR! Linux 3.13.0-39-generic
npm ERR! argv "~/.nvm/v0.11.14/bin/node" "~/.nvm/v0.11.14/bin/npm" "install" "node-sass"
npm ERR! node v0.11.14
npm ERR! npm  v2.0.0
npm ERR! code ELIFECYCLE
npm ERR! node-sass@1.2.3 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@1.2.3 postinstall script.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.
jenkins@jenkins:XXX$

I've googled all over the place, but it seems as though this is a test failure and not anything to do with the actual build failing.

@ixtli
Copy link
Author

ixtli commented Nov 20, 2014

If it helps at all, I got here because broccoli-sass@0.3.2 needs this as a dependency (obviously.)

@ixtli
Copy link
Author

ixtli commented Nov 20, 2014

I've done a little poking at the build and it seems like line 181 in lib/index.js ( https://github.com/sass/node-sass/blob/master/lib/index.js#L181 ) tries to require a module named by a function getBinding(). On my system this function returns the string /var/lib/jenkins/node-sass/vendor/linux-x64/binding.node . The file at this path is a binary. Perhaps this is functionality of nodejs that I'm not aware of but I don't quite see how require() could use such a file...

As an experiment i gave it execute perms but that didn't do anything.

A node-sass/vendor/linux-x64/binding.node of the file is as follows:

jenkins@jenkins:~/node-sass$ stat XXX/node-sass/vendor/linux-x64/binding.node
  File: `XXX/node-sass/vendor/linux-x64/binding.node'
  Size: 1784574         Blocks: 3488       IO Block: 4096   regular file
Device: ca01h/51713d    Inode: 296639      Links: 1
Access: (0775/-rwxrwxr-x)  Uid: (  106/ jenkins)   Gid: (  113/ jenkins)
Access: 2014-11-20 18:49:42.417310000 -0500
Modify: 2014-11-20 18:45:40.505310000 -0500
Change: 2014-11-20 18:49:38.513310000 -0500
 Birth: -

ixtli referenced this issue in sass/node-sass-binaries Nov 21, 2014
@brancusi
Copy link

Getting this error as well. Building on OSX 10.10.1

I feel like this just started recently.

@ixtli
Copy link
Author

ixtli commented Nov 21, 2014

Yes I believe that it's due to the most recent build of binding.node .
Something's just wrong with the dylib i think.

2014-11-20 22:29 GMT-05:00 Aram Zadikian notifications@github.com:

Getting this error as well. Building on OSX 10.10.1

I feel like this just started recently.


Reply to this email directly or view it on GitHub
#550 (comment).

@ixtli
Copy link
Author

ixtli commented Nov 21, 2014

I'm pretty sure this is the offending build: sass/node-sass-binaries@9d6417d

@rDarge
Copy link

rDarge commented Nov 21, 2014

Getting this error as well - OSX 10.9.4
Snippet of the npm-debug.log below

9067 verbose linkMans node-sass@1.2.3
9068 verbose rebuildBundles node-sass@1.2.3
9069 verbose rebuildBundles [ '.bin',
9069 verbose rebuildBundles   'chalk',
9069 verbose rebuildBundles   'cross-spawn',
9069 verbose rebuildBundles   'gaze',
9069 verbose rebuildBundles   'get-stdin',
9069 verbose rebuildBundles   'meow',
9069 verbose rebuildBundles   'mkdirp',
9069 verbose rebuildBundles   'mocha',
9069 verbose rebuildBundles   'nan',
9069 verbose rebuildBundles   'object-assign',
9069 verbose rebuildBundles   'replace-ext',
9069 verbose rebuildBundles   'request',
9069 verbose rebuildBundles   'shelljs' ]
9070 verbose gentlyRm vacuuming /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/.bin/node-sass
9071 info install node-sass@1.2.3
9072 verbose unsafe-perm in lifecycle true
9073 info postinstall node-sass@1.2.3
9074 verbose unsafe-perm in lifecycle true
9075 info node-sass@1.2.3 Failed to exec postinstall script
9076 verbose unlock done using /Users/New/.npm/_locks/node-sass-a4023839e194b21f.lock for /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/node-sass
9077 verbose about to build /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass
9078 verbose unlock done using /Users/New/.npm/_locks/broccoli-sass-000a5f85d6f954ae.lock for /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass
9079 verbose stack Error: Exit status 1
9079 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:212:16)
9079 verbose stack     at EventEmitter.emit (events.js:110:17)
9079 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:14:12)
9079 verbose stack     at ChildProcess.EventEmitter.emit (events.js:110:17)
9079 verbose stack     at maybeClose (child_process.js:992:16)
9079 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:1059:5)
9080 verbose pkgid node-sass@1.2.3
9081 verbose cwd /Users/New/Documents/InboxDashboard
9082 error Darwin 13.3.0
9083 error argv "node" "/usr/local/bin/npm" "install" "broccoli-sass"
9084 error node v0.11.13
9085 error npm  v2.1.10
9086 error code ELIFECYCLE
9087 error node-sass@1.2.3 postinstall: `node scripts/build.js`
9087 error Exit status 1
9088 error Failed at the node-sass@1.2.3 postinstall script 'node scripts/build.js'.
9088 error This is most likely a problem with the node-sass package,
9088 error not with npm itself.
9088 error Tell the author that this fails on your system:
9088 error     node scripts/build.js
9088 error You can get their info via:
9088 error     npm owner ls node-sass
9088 error There is likely additional logging output above.
9089 verbose exit [ 1, true ]
9090 verbose unbuild node_modules/broccoli-sass/node_modules/node-sass
9091 info preuninstall node-sass@1.2.3
9092 info uninstall node-sass@1.2.3
9093 verbose unbuild rmStuff node-sass@1.2.3 from /Users/New/Documents/InboxDashboard/node_modules
9094 verbose unbuild rmStuff in /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules
9095 verbose gentlyRm verifying that /Users/New/Documents/InboxDashboard is managed by npm
9096 silly cacheAndTest /Users/New/Documents/InboxDashboard is not inside /Users/New/Documents/InboxDashboard/node_modules
9097 silly isManaged /Users/New/Documents/InboxDashboard is not inside /Users/New/Documents/InboxDashboard/node_modules
9098 silly cacheAndTest /Users/New/Documents/InboxDashboard is inside /Users/New/Documents/InboxDashboard
9099 silly gentlyRm /Users/New/Documents/InboxDashboard is managed by npm
9100 silly gentlyRm /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/.bin/node-sass is under /Users/New/Documents/InboxDashboard
9101 verbose gentlyRm vacuuming /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/.bin/node-sass up to /Users/New/Documents/InboxDashboard
9102 silly gentlyRm removing /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/.bin/node-sass
9103 silly gentlyRm removing /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/.bin
9104 silly gentlyRm quitting because other entries in /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules
9105 info postuninstall node-sass@1.2.3
9106 verbose gentlyRm vacuuming /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/node-sass
9107 silly gentlyRm purging /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules/node-sass
9108 silly gentlyRm quitting because other entries in /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass/node_modules
9109 verbose unbuild node_modules/broccoli-sass
9110 info preuninstall broccoli-sass@0.3.3
9111 info uninstall broccoli-sass@0.3.3
9112 verbose unbuild rmStuff broccoli-sass@0.3.3 from /Users/New/Documents/InboxDashboard/node_modules
9113 info postuninstall broccoli-sass@0.3.3
9114 verbose gentlyRm vacuuming /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass
9115 silly gentlyRm purging /Users/New/Documents/InboxDashboard/node_modules/broccoli-sass
9116 silly gentlyRm removing /Users/New/Documents/InboxDashboard/node_modules
9117 silly gentlyRm finished vacuuming up to /Users/New/Documents/InboxDashboard

@rDarge
Copy link

rDarge commented Nov 21, 2014

For now I'm getting around it by specifying node-sass version 1.2.2 explicitly in my package .json file

@ixtli
Copy link
Author

ixtli commented Nov 21, 2014

Interesting. I guess I'll try to force broccoli-sass compiler to use an
older version. It certainly wont hurt anything, it's not like im using
bleeding edge features.

On Fri Nov 21 2014 at 1:52:33 PM Ryan Darge notifications@github.com
wrote:

For now I'm getting around it by specifying node-sass version 1.2.2
explicitly in my package .json file


Reply to this email directly or view it on GitHub
#550 (comment).

@wayne-o
Copy link

wayne-o commented Nov 22, 2014

Also getting this, also forcing 1.2.2 seems to yield better results

@Martii
Copy link

Martii commented Nov 23, 2014

Not getting this here but it's also not Ubuntu.

Are any of you using your distros releases instead of building yourself?

$ npm install node-sass
npm WARN package.json bootstrap-markdown@2.7.0 'repositories' (plural) Not supported. Please pick one as the 'repository' field
npm WARN package.json mu2@0.5.20 No repository field.
\
> node-sass@1.2.3 install /home/user/repo/git/oujs/martii/OpenUserJS.org/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /home/user/repo/git/oujs/martii/OpenUserJS.org/node_modules/node-sass/vendor/linux-x64/binding.node

> node-sass@1.2.3 postinstall /home/user/repo/git/oujs/martii/OpenUserJS.org/node_modules/node-sass
> node scripts/build.js

`linux-x64` exists; testing
Binary is fine; exiting
node-sass@1.2.3 node_modules/node-sass
├── get-stdin@3.0.0
├── object-assign@1.0.0
├── replace-ext@0.0.1
├── shelljs@0.3.0
├── nan@1.4.1
├── mkdirp@0.5.0 (minimist@0.0.8)
├── cross-spawn@0.2.3 (lru-cache@2.5.0)
├── chalk@0.5.1 (escape-string-regexp@1.0.2, ansi-styles@1.1.0, supports-color@0.2.0, strip-ansi@0.3.0, has-ansi@0.1.0)
├── gaze@0.5.1 (globule@0.1.0)
├── mocha@2.0.1 (escape-string-regexp@1.0.2, diff@1.0.8, growl@1.8.1, commander@2.3.0, jade@0.26.3, glob@3.2.3, debug@2.0.0)
└── meow@2.0.0 (minimist@1.1.0, camelcase-keys@1.0.0, indent-string@1.2.0)

$ node -v
v0.10.32

$ npm --version
2.1.8

... failing on Ubuntu 12.04.5

Current Ubuntu is mentioned to be Ubuntu 14.04.1 LTS. I can try building this on a spare machine if it helps anyone to debug.

@MrOrz
Copy link

MrOrz commented Nov 23, 2014

webpack sass-loader brought me here.
Adding "node-sass": "1.2.2" in the dependency did the trick. Thanks @Garlandicus !

@Martii
Copy link

Martii commented Nov 23, 2014

Here's some results:

Ubuntu 14.04.1 LTS

$ node -v
v0.10.34-pre

$ npm -v
1.4.28

$ npm install node-sass
/
> node-sass@1.2.3 install /home/user/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /home/user/node_modules/node-sass/vendor/linux-x64/binding.node

> node-sass@1.2.3 postinstall /home/user/node_modules/node-sass
> node scripts/build.js

`linux-x64` exists; testing
Binary is fine; exiting
node-sass@1.2.3 ../node_modules/node-sass
├── get-stdin@3.0.2
├── object-assign@1.0.0
├── replace-ext@0.0.1
├── cross-spawn@0.2.3 (lru-cache@2.5.0)
├── mkdirp@0.5.0 (minimist@0.0.8)
├── shelljs@0.3.0
├── nan@1.4.1
├── chalk@0.5.1 (escape-string-regexp@1.0.2, ansi-styles@1.1.0, supports-color@0.2.0, has-ansi@0.1.0, strip-ansi@0.3.0)
├── meow@2.0.0 (minimist@1.1.0, camelcase-keys@1.0.0, indent-string@1.2.0)
├── gaze@0.5.1 (globule@0.1.0)
├── mocha@2.0.1 (escape-string-regexp@1.0.2, diff@1.0.8, growl@1.8.1, commander@2.3.0, glob@3.2.3, debug@2.0.0, jade@0.26.3)
└── request@2.48.0 (caseless@0.7.0, json-stringify-safe@5.0.0, aws-sign2@0.5.0, forever-agent@0.5.2, stringstream@0.0.4, oauth-sign@0.5.0, tunnel-agent@0.4.0, node-uuid@1.4.1, qs@2.3.3, mime-types@1.0.2, combined-stream@0.0.7, form-data@0.1.4, bl@0.9.3, tough-cookie@0.12.1, http-signature@0.10.0, hawk@1.1.1)

@PMK
Copy link

PMK commented Nov 23, 2014

Same here with a fresh install on Mac OS 10.9.4:

$ npm install node-sass
\
> node-sass@1.2.3 install node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at node_modules/node-sass/vendor/darwin-x64/binding.node

> node-sass@1.2.3 postinstall node_modules/node-sass
> node scripts/build.js

`darwin-x64` exists; testing
module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (node_modules/node-sass/lib/index.js:181:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
npm ERR! Darwin 13.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "node-sass"
npm ERR! node v0.11.14
npm ERR! npm  v2.1.9
npm ERR! code ELIFECYCLE

npm ERR! node-sass@1.2.3 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@1.2.3 postinstall script 'node scripts/build.js'
..etc..

Edit:
Thanks to sass/node-sass-binaries@9d6417d#commitcomment-8683794 I switched to node 0.10.33 and solves the problem.

@YourDeveloperFriend
Copy link

I also was able to fix the problem by switching from node 0.11.x to 0.10.x.

@ixtli
Copy link
Author

ixtli commented Nov 24, 2014

Yes I think it's been well shown that the binary breaks when required by node v0.11.x which is in development. This means that you should definitely be using 0.10.x in production :)

(That said, I think it's reasonable to try to make node modules work with the current development branch of node or to document when it's known to break. Which of course means building version specific tests. The amount of references to this issue seems to show how many people are using bleeding edge versions of v8/node to develop with.)

@NickHeiner
Copy link

👍 As others have mentioned, I've only experienced this issue on node v0.11.

@joshsmith
Copy link

I'm explicitly depending on node-sass 1.2.2 and am on node v0.10.33 and am still experiencing this issue on Heroku.

@mgol
Copy link
Contributor

mgol commented Nov 28, 2014

Same on OS X 10.10.1, Node 0.11.14, npm 2.1.11. On Node 0.10.33 everything works fine, probably because it's pre-built.

@aamirl
Copy link

aamirl commented Dec 2, 2014

Same issue here on Windows 7-64, Node 0.11.9, npm 2.1.11. Running it with koa so can't migrate back down to node 1.10 :(

Is there a current work-around or force-install that works?

@ghost
Copy link

ghost commented Dec 14, 2014

Same issue with ubuntu 14.04, npm 2.1.1.

@LoicMahieu
Copy link

Same issue with node v0.11.14 but works fine for v0.10.33

@enzy
Copy link

enzy commented Dec 15, 2014

Fails on Travis CI with v0.11.14 target... https://travis-ci.org/manGoweb/mango-cli/jobs/44083201#L154

@agconti
Copy link

agconti commented Dec 16, 2014

@enzy same issue. +1

@am11
Copy link
Contributor

am11 commented Dec 16, 2014

We do not support njs nightly v0.11.* at this point, but only the stable one v0.10.33.

From the solution perspective, this is same issue as #517. Lets follow it there.

@briandela
Copy link

Getting this issue with Node 0.12 now. Any ideas how to solve this for node v0.12.

@kevinSuttle
Copy link

Same.
OSX 10.10.2.
Node v0.12 Installed via brew
Even tried node-sass@2.0.0-beta: no dice

@am11
Copy link
Contributor

am11 commented Feb 9, 2015

@briandela @kevinSuttle see #653.

@mcgwiz
Copy link

mcgwiz commented Feb 9, 2015

On Yosemite, node 0.12.0. Just resorted to this. See section 3b of the accepted answer in order to downgrade node to 0.10.33.

@Martii
Copy link

Martii commented Feb 9, 2015

Latest 0.10.x is 0.10.36 btw

@am11
Copy link
Contributor

am11 commented Feb 9, 2015

Guys lets not discuss scattered/random matters under closed issues.

The related issue is opened here: #655

If you are facing particular issue, search the issue tracker for the opened ones first, if not found open a new one.

@Martii, and 0.10.36 is supported by v2.0.0-beta.

@mcgwiz, see the comments at #653. You can build the binary for Mac for both io.js and node.js v0.12.

@Martii
Copy link

Martii commented Feb 9, 2015

Would be nice if GH would mirror the div.state-closed below too... didn't realize it was closed since I'm taken straight to the end here. My apologies yet again.

@am11
Copy link
Contributor

am11 commented Feb 9, 2015

@Martii, you can send feedback to GH team, they are very receptive (i.e. at the minimum, they reply to every email sooner or later).

@laurilehmijoki
Copy link

I'm seeing

Error: Module did not self-register.
    at Error (native)              
    at Module.load (module.js:355:32)                                                                  
    at Function.Module._load (module.js:310:12)                                                       
    at Module.require (module.js:365:17)                                                             
    at require (module.js:384:17)                                                                   
    at Object.<anonymous> (/Users/llehmijo/myapp/node_modules/node-sass
/lib/index.js:181:15)                                                                                 
    at Module._compile (module.js:460:26)                                                            
    at Object.Module._extensions..js (module.js:478:10)                                             
    at Module.load (module.js:355:32)                                                              
    at Function.Module._load (module.js:310:12)  

When node-sass version is 1.2.3 and Node.js version is 0.12.0.

Update: problem solved by upgrading node-sass from 1.2.3 to 2.0.1.

@xzyfer
Copy link
Contributor

xzyfer commented Feb 13, 2015

1.2.3 does not support node 0.12. Upgrade to 2.0.1 for for 0.12 support.
On 13 Feb 2015 17:16, "Lauri Lehmijoki" notifications@github.com wrote:

I'm seeing

Error: Module did not self-register.
at Error (native)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/Users/llehmijo/myapp/node_modules/node-sass
/lib/index.js:181:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)

When node-sass version is 1.2.3 and Node.js version is 0.12.0.


Reply to this email directly or view it on GitHub
#550 (comment).

@coledot
Copy link

coledot commented May 6, 2015

Still having this issue on OSX 10.10:

> node-sass@1.2.3 install node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at node_modules/node-sass/vendor/darwin-x64/binding.node

> node-sass@1.2.3 postinstall node_modules/node-sass
> node scripts/build.js

`darwin-x64` exists; testing
module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (node_modules/node-sass/lib/index.js:181:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.2
npm ERR! npm  v2.7.5
npm ERR! code ELIFECYCLE

npm ERR! node-sass@1.2.3 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@1.2.3 postinstall script 'node scripts/build.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     node_modules/npm-debug.log

Had to roll back to 1.2.2.

@am11
Copy link
Contributor

am11 commented May 6, 2015

@coledot
The latest stable version of node-sass is v3.0.0. You are using an ancient version v1.2.2/3.
Try out v3 to find out what are you missing. ;)

@charmeleon-zz
Copy link

I also had this version running node 0.11.13, Ubuntu 14.04. It's used as a dependency for gulp-sass so I can't change the version. I can confirm that using node 0.10.29 makes the error go away (but then I feel icky)

@xzyfer
Copy link
Contributor

xzyfer commented May 27, 2015

Node 0.11 is simply unsupported. This will not change. Updating to 0.12
will also resolve the issue.
On 27 May 2015 12:27, "Charmeleon" notifications@github.com wrote:

I also had this version running node 0.11.13, Ubuntu 14.04. It's used as a
dependency for gulp-sass so I can't change the version. I can confirm that
using node 0.10.29 makes the error go away (but then I feel icky)


Reply to this email directly or view it on GitHub
#550 (comment).

jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this issue Apr 7, 2024
Output leading zeros on numbers as seen in input (Fixes sass#550)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests