You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 24, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 24, 2024. It is now read-only.
Now that Apple is releasing ARM based chips, opening a general tracking issue. This will likely hit the same lack of CI support that we run into for general ARM support.
I just tried building a project on M1 Macbook air and got architecture not supported error.
node sass does not yet support your current environment: os x unsupported architecture (arm64)
Is there instructions for building it on arm64? I can try building it and see how it goes. thanks
Reacted by Emanuele, JD, Arne Wiese and Matthew Zagaja
EDIT: for anyone trying to build assets on an ARM64 device such as the RPi4 with Webpack through sass-loader, you can get it working by replacing the dependency node-sass with sass.
Reacted by Matt, Max Coplan, Connor Lurring, Development lexos GmbH, JD, Jim Hodapp, Michael Chang and Tiago Parreira
We really need official binary support for the ARM64 arch. ARM CPU is slowly but surely being an important part of computing. Since node-sass is a common dependency for JS projects, I'm sure that more and more users will face this issue and come to here.
Reacted by Matt, Max Coplan, Emanuele, JD, weiyang.su and Andy Aylward
We'd love to support the new Apple M1 chips however we're blocked until there is a free hosted CI solution that supports that hardware. Currently we're tracking these issues for github actions
We'd love to support the new Apple M1 chips however we're blocked until there is a free hosted CI solution that supports that hardware. Currently we're tracking these issues for github actions
When I tried to install node-sass@5 with node@15, recursively printing out these message below and never finish installation.
2 warnings generated.
c++ -o Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o ../src/libsass/src/ast_fwd_decl.cpp '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DLIBSASS_VERSION="3.5.5"' -I/Users/xxx/Library/Caches/node-gyp/15.4.0/include/node -I/Users/xxx/Library/Caches/node-gyp/15.4.0/src -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/openssl/config -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/openssl/openssl/include -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/uv/include -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/zlib -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/v8/include -I../src/libsass/include -O3 -gdwarf-2 -mmacosx-version-min=10.7 -arch arm64 -Wall -Wendif-labels -W -Wno-unused-parameter -std=c++11 -stdlib=libc++ -fno-strict-aliasing -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o.d.raw -c
In file included from ../src/libsass/src/ast_fwd_decl.cpp:1:
../src/libsass/src/ast.hpp:1614:25: warning: loop variable 'numerator' of type 'const
std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>'
[-Wrange-loop-analysis]
for (const auto numerator : numerators)
^
../src/libsass/src/ast.hpp:1614:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent
copying
for (const auto numerator : numerators)
^~~~~~~~~~~~~~~~~~~~~~
&
../src/libsass/src/ast.hpp:1616:25: warning: loop variable 'denominator' of type 'const
std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>'
[-Wrange-loop-analysis]
for (const auto denominator : denominators)
^
../src/libsass/src/ast.hpp:1616:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent
copying
for (const auto denominator : denominators)
^~~~~~~~~~~~~~~~~~~~~~~~
&
On Thu, 31 Dec 2020, 6:38 pm Ho-Yang Tsai, ***@***.***> wrote:
When I tried to install ***@***.***, recursively printing out these
message below
2 warnings generated.
c++ -o Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o ../src/libsass/src/ast_fwd_decl.cpp '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DLIBSASS_VERSION="3.5.5"' -I/Users/xxx/Library/Caches/node-gyp/15.4.0/include/node -I/Users/xxx/Library/Caches/node-gyp/15.4.0/src -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/openssl/config -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/openssl/openssl/include -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/uv/include -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/zlib -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/v8/include -I../src/libsass/include -O3 -gdwarf-2 -mmacosx-version-min=10.7 -arch arm64 -Wall -Wendif-labels -W -Wno-unused-parameter -std=c++11 -stdlib=libc++ -fno-strict-aliasing -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o.d.raw -c
In file included from ../src/libsass/src/ast_fwd_decl.cpp:1:
../src/libsass/src/ast.hpp:1614:25: warning: loop variable 'numerator' of type 'const
std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>'
[-Wrange-loop-analysis]
for (const auto numerator : numerators)
^
../src/libsass/src/ast.hpp:1614:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent
copying
for (const auto numerator : numerators)
^~~~~~~~~~~~~~~~~~~~~~
&
../src/libsass/src/ast.hpp:1616:25: warning: loop variable 'denominator' of type 'const
std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>'
[-Wrange-loop-analysis]
for (const auto denominator : denominators)
^
../src/libsass/src/ast.hpp:1616:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent
copying
for (const auto denominator : denominators)
^~~~~~~~~~~~~~~~~~~~~~~~
&
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3033 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAENSWAX5NCPETX2IZMBMJ3SXQS6ZANCNFSM4T77ZYFA>
.
Hi,
I'm facing this error when running compilation with MB Air M1: Error: Node Sass does not yet support your current environment: OS X Unsupported architecture (arm64) with Unsupported runtime (88) For more information on which environments are supported please see:
Apple silicon support would be great!
Reacted by Development lexos GmbH, JD, Dawid aka Cactus, Matthew Zagaja, Andrew Boyd and César Del Solar
We'd love to support the new Apple M1 chips however we're blocked until there is a free hosted CI solution that supports that hardware. Currently we're tracking these issues for github actions
You could start with ARM on raspberry pi....
Many many solutions running on rpi....
Might be true, but since it never run on raspberry pi's before, but was used by a huge number of developers on Macs, Mac should be prioritised. Anyway, raspberry pi should follow up if possible. ;-)
We'd love to support the new Apple M1 chips however we're blocked until there is a free hosted CI solution that supports that hardware. Currently we're tracking these issues for github actions
You could start with ARM on raspberry pi....
Many many solutions running on rpi....
Might be true, but since it never run on raspberry pi's before, but was used by a huge number of developers on Macs, Mac should be prioritised. Anyway, raspberry pi should follow up if possible. ;-)
Chicken and egg.......... If there's no solution for pi, its not going to run there; if there's no possibility to deliver support for new M1, then close that other gap
I've worked with a macbook m1 chip 8gb of ram for almost a month. Each day has been painfully slow because of being stuck with nodejs 14 since node-sass doesn't work with the arm version of nodejs.
I'm finally giving up and upgrading to 16gb ram...
Hi,
I'm facing same error when running on MB Pro M1 (16GB RAM):
Error: Node Sass does not yet support your current environment: OS X Unsupported architecture (arm64) with Unsupported runtime (88) For more information on which environments are supported please see:
Activity
woolfel commentedon Dec 12, 2020
I just tried building a project on M1 Macbook air and got architecture not supported error.
node sass does not yet support your current environment: os x unsupported architecture (arm64)
Is there instructions for building it on arm64? I can try building it and see how it goes. thanks
o-alquimista commentedon Dec 16, 2020
Same for Raspberry Pi 4 :(
EDIT: for anyone trying to build assets on an ARM64 device such as the RPi4 with Webpack through
sass-loader, you can get it working by replacing the dependencynode-sasswith sass.kycfeel commentedon Dec 17, 2020
We really need official binary support for the ARM64 arch. ARM CPU is slowly but surely being an important part of computing. Since
node-sassis a common dependency for JS projects, I'm sure that more and more users will face this issue and come to here.xzyfer commentedon Dec 17, 2020
We'd love to support the new Apple M1 chips however we're blocked until there is a free hosted CI solution that supports that hardware. Currently we're tracking these issues for github actions
Ton-O commentedon Dec 17, 2020
You could start with ARM on raspberry pi....
Many many solutions running on rpi....
woolfel commentedon Dec 17, 2020
circleCI announced self-hosted here https://circleci.com/blog/self-hosted-runners-add-arm-support-to-circleci/
I'm willing to donate some raspberry pi4 if circleCI self-hosted is an option you want to consider.
woolfel commentedon Dec 17, 2020
I have several raspberry pi that I can setup with circleCI self-hosted.
aminroosta commentedon Dec 24, 2020
hoyangtsai commentedon Dec 31, 2020
When I tried to install node-sass@5 with node@15, recursively printing out these message below and never finish installation.
xzyfer commentedon Dec 31, 2020
hakey1408 commentedon Dec 31, 2020
Hi,
I'm facing this error when running compilation with MB Air M1:
Error: Node Sass does not yet support your current environment: OS X Unsupported architecture (arm64) with Unsupported runtime (88) For more information on which environments are supported please see:Apple silicon support would be great!
nschonni commentedon Jan 1, 2021
lexos-development commentedon Jan 5, 2021
Might be true, but since it never run on raspberry pi's before, but was used by a huge number of developers on Macs, Mac should be prioritised. Anyway, raspberry pi should follow up if possible. ;-)
Ton-O commentedon Jan 6, 2021
Chicken and egg.......... If there's no solution for pi, its not going to run there; if there's no possibility to deliver support for new M1, then close that other gap
cwagner22 commentedon Jan 13, 2021
I've worked with a macbook m1 chip 8gb of ram for almost a month. Each day has been painfully slow because of being stuck with nodejs 14 since node-sass doesn't work with the arm version of nodejs.
I'm finally giving up and upgrading to 16gb ram...
mzagaja commentedon Jan 19, 2021
For Google wanderers like me trying to get their node-sass working on the site in the meantime the magic trick to use Rosetta 2 is:
jhodapp commentedon Jan 23, 2021
MokryPatrik commentedon Jan 25, 2021
Hi,
I'm facing same error when running on MB Pro M1 (16GB RAM):
Error: Node Sass does not yet support your current environment: OS X Unsupported architecture (arm64) with Unsupported runtime (88) For more information on which environments are supported please see:
parreirat commentedon Jan 25, 2021
MokryPatrik commentedon Jan 25, 2021
This worked for me https://stackoverflow.com/a/64902152, not the cleanest solution but it works without any modifications in the project.
nschonni commentedon Jan 25, 2021
Locked the thread as per the first issue, this is about tracking when we'll officially support these builds. We can't till GitHub actions adds support
nschonni commentedon Jul 26, 2021
nschonni commentedon Oct 2, 2023
Looks like the runners are available actions/runner-images#8439
edit: looks like it's still paid only, so we're not there yet
nschonni commentedon Jan 31, 2024
Runner support landed for OSS https://github.blog/changelog/2024-01-30-github-actions-introducing-the-new-m1-macos-runner-available-to-open-source/
Starting to test it out in #3390