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

will npm download the newest subversion by default?(support needed) #2934

@appleyuchi

Description

@appleyuchi

apologise that copy node-sass's official hints into following table

version name command my version
NPM version npm -v 6.11.3
Node version node -v v12.11.1
Node Process node -p process.versions node: '12.11.1',
v8: '7.7.299.11-node.12',
uv: '1.32.0',
zlib: '1.2.11',
brotli: '1.0.7',
ares: '1.15.0',
modules: '72',
nghttp2: '1.39.2',
napi: '5',
llhttp: '1.1.4',
http_parser: '2.8.0',
openssl: '1.1.1c',
cldr: '35.1',
icu: '64.2',
tz: '2019a',
unicode: '12.1'
Node Platform node -p process.platform linux
Node architecture node -p process.arch x64
node-sass version node -p "require('node-sass').info" node-sass 4.14.1 (Wrapper)[JavaScript]
libsass 3.5.5 (Sass Compiler) [C/C++]
npm node-sass versions npm ls node-sass [email protected] /home/appleyuchi
└── [email protected]

package.json is:
https://paste.ubuntu.com/p/7QNx7qPjrr/

My question is :
why did npm cichoose linux-x64-72_binding.node which has been deleted in the following link?
#2648

I mean,why the 72above is selected?
just newest by default or set by somewhere?

aplogise that if github is not the right place to ask question,
point this to me please and I'll ask it on quora/stackoverflow,etc...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions