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.

Apple ARM Support #3033

Open
Open

Description

@nschonni

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.

  • Need a CI provider to test and produce binaries
  • Updates to supported architecture

This would likely come as a 5.0.1 or later, and there is no plan to add support for older versions as per https://github.com/sass/node-sass#node-version-support-policy

Activity

  1. woolfel commented on Dec 12, 2020

    @woolfel

    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

  2. o-alquimista commented on Dec 16, 2020

    @o-alquimista

    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 dependency node-sass with sass.

  3. kycfeel commented on Dec 17, 2020

    @kycfeel

    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.

  4. xzyfer commented on Dec 17, 2020

    @xzyfer
    Contributor

    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

  5. Ton-O commented on Dec 17, 2020

    @Ton-O

    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....

  6. woolfel commented on Dec 17, 2020

    @woolfel

    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.

  7. woolfel commented on Dec 17, 2020

    @woolfel

    I have several raspberry pi that I can setup with circleCI self-hosted.

  8. aminroosta commented on Dec 24, 2020

    @aminroosta
  9. hoyangtsai commented on Dec 31, 2020

    @hoyangtsai

    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)
                 ^~~~~~~~~~~~~~~~~~~~~~~~
                            &
    
  10. xzyfer commented on Dec 31, 2020

    @xzyfer
    Contributor
  11. hakey1408 commented on Dec 31, 2020

    @hakey1408

    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!

  12. nschonni commented on Jan 1, 2021

    @nschonni
    Author
  13. lexos-development commented on Jan 5, 2021

    @lexos-development

    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. ;-)

  14. Ton-O commented on Jan 6, 2021

    @Ton-O

    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

  15. cwagner22 commented on Jan 13, 2021

    @cwagner22

    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...

  16. mzagaja commented on Jan 19, 2021

    @mzagaja

    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:

    rm -rf node_modules
    npm install --target_arch=x64
  17. jhodapp commented on Jan 23, 2021

    @jhodapp
  18. MokryPatrik commented on Jan 25, 2021

    @MokryPatrik

    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:

  19. parreirat commented on Jan 25, 2021

    @parreirat
  20. MokryPatrik commented on Jan 25, 2021

    @MokryPatrik

    This worked for me https://stackoverflow.com/a/64902152, not the cleanest solution but it works without any modifications in the project.

  21. locked as off topic and limited conversation to collaborators on Jan 25, 2021
  22. nschonni commented on Jan 25, 2021

    @nschonni
    ContributorAuthor

    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

  23. pinned this issue on Apr 23, 2021
  24. nschonni commented on Jul 26, 2021

    @nschonni
    Author
  25. nschonni commented on Oct 2, 2023

    @nschonni
    ContributorAuthor

    Looks like the runners are available actions/runner-images#8439

    edit: looks like it's still paid only, so we're not there yet

  26. nschonni commented on Jan 31, 2024

    @nschonni
    ContributorAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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