We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be possible to backport #3209 to node-sass 6.0+?
Motivation:
It would avoid the following error:
env: python: No such file or directory
Workaround: Use selective dependency resolutions strategy in package.json:
"resolutions": { "node-sass/node-gyp": "8" },
npm -v
node -v
node -p process.versions
{ node: '16.13.2', v8: '9.4.146.24-node.14', uv: '1.42.0', zlib: '1.2.11', brotli: '1.0.9', ares: '1.18.1', modules: '93', nghttp2: '1.45.1', napi: '8', llhttp: '6.0.4', openssl: '1.1.1l+quic', cldr: '39.0', icu: '69.1', tz: '2021a', unicode: '13.0', ngtcp2: '0.1.0-DEV', nghttp3: '0.1.0-DEV' }
node -p process.platform
node -p process.arch
node -p "require('node-sass').info"
node-sass 6.0.1 (Wrapper) [JavaScript] libsass 3.5.5 (Sass Compiler) [C/C++]
npm ls node-sass
nextjsproject@0.0.2 /Users/yurilima/Projects/nextjsproject ├─┬ next@12.0.7 │ └── node-sass@6.0.1 deduped └── node-sass@6.0.1
The text was updated successfully, but these errors were encountered:
It's been requested before like #3106 (comment) to backport changes, but we don't support more than one active release
Sorry, something went wrong.
No branches or pull requests
It would be possible to backport #3209 to node-sass 6.0+?
Motivation:
It would avoid the following error:
Workaround: Use selective dependency resolutions strategy in package.json:
npm -v
): 8.1.2node -v
): v16.13.2node -p process.versions
):node -p process.platform
): darwinnode -p process.arch
): arm64node -p "require('node-sass').info"
):npm ls node-sass
):The text was updated successfully, but these errors were encountered: