New Macs with the M1 chip may have issues running the Prototype Kit #1000
Labels
🐛 Bug
Something isn't working the way it should (including incorrect wording in documentation)
Comments
|
via @36degrees : Running software under Rosetta |
joelanman
added
the
🐛 Bug
|
I've tried running the kit on my M1 MacBook Air under Node 14. Rosetta seemed to kick in automatically as I could see Node running with Intel architecture – it all 'just worked'. I've verified that 'Open using Rosetta' is not checked for the Terminal app. I wasn't able to replicate a true 'blank slate' as I'd already got
@frankieroberto what issues were you seeing with Node 14 that prompted you to use Node 15 instead? |
|
I guess the other thing that I'd 'already done' is installed Rosetta 2. I think Apple prompts you to install it when it detects it's needed, but I don't know if that works for command line applications? |
|
@36degrees interesting! I get a compile error when trying to run How did you install node and nvm? When I run |
I installed it using the installer for 14.16.1 from https://nodejs.org/en/, which I think overwrote the v12 install that I guess comes with macOS? |
|
@36degrees ah. I think I went straight to installing Weirdly, having gotten the kit working with node 15, it now also runs using node 14, although I do still get a whole bunch of sass compilation warnings when running Hopefully this will all get smoothed out over the coming year! |
|
Nope, seems to work fine… (albeit tested with a slightly older version) 🤔 Trying to install latest 14.x through nvm at the min but it's still compiling… ⏱️ |
|
OK, testing with 14.6.1 under nvm I've now got it to throw warnings during Terminal output |
|
@36degrees yeah, I get the same now – but before it failed! I wonder if it works ok once you've successfully installed all the dependencies once (eg using node 15), as they get shared somehow? 🤷♂️ |
joelanman
changed the title
joelanman
changed the title
|
One user on x-gov found it better to use Node 14 under Rosetta:
|
|
@36degrees do you know if they did anything specific to run under rosetta that we could write up, at least in the description of this issue? |
|
Randomly stumbled on this thread while googling for an repeating error of "warning: loop variable 'denominator'" when doing an npm install. When I got the M1 Mac Mini I had to upgrade our Node version 14.16.0 to 14.17.4. After upgrading to 14.17.4 everything is fine, no need to force Rosetta or anything. I have heard upgrading all the way to 15.x.x/16.x.x will also work well on the M1. |
|
the latest version of the Prototype Kit (v10) support Node 16, and updates node sass, hopefully this resolves this issue but more testing is needed to verify - if you can test on M1 please let us know! |
|
recently helped someone on an m1 mac install, and we had to use this command for the npm install step: I suspect it may work without if you have xcode developer tools to compile node sass |
|
The kit now works on M1 macs, please update to the latest version of the kit |
|
I encountered some |
|
I found installing On my machine I fixed the problem by using |
|
An update to this - my very new M1 Mac didn't have a version of Python installed out of the box (doing |
|
Apple has stopped bundling Python 2.x in the operating system as of macOS 12.3. Users must now either install it manually, or if they install XCode, they will have Python 3.x installed instead. This was apparently announced as happening back in 2019, though it seems to have flown under a lot of radars and it's a bit weird that they did the removal in a minor macOS release. |
|
Tested again with @domoscargin, we confirmed that the kit no longer installs on M1. We found 2 workarounds:
This will give warnings when the kit runs, but seems to work |
|
Note that replacing This probably isn't a huge issue for prototyping, but something to be aware of. |
lfdebrux
added a commit
that referenced
this issue
Mar 31, 2022
We want to use `sass` instead of `node-sass` because `node-sass` does not support M1 Macs (see issue #1000). We have to replace use of slash for division with `math.div` to avoid deprecation warnings. We also use sync for performance and silence warnings (for now). Co-authored-by: Natalie Carey <natalie.carey@digital.cabinet-office.gov.uk> Co-authored-by: Joe Lanman <joe.lanman@digital.cabinet-office.gov.uk> Co-authored-by: Laurence de Bruxelles <laurence.debruxelles@digital.cabinet-office.gov.uk>
lfdebrux
added a commit
that referenced
this issue
Mar 31, 2022
We want to use `sass` instead of `node-sass` because `node-sass` does not support M1 Macs (see issue #1000). We have to replace use of slash for division with `math.div` to avoid deprecation warnings. We also use sync for performance and silence warnings (for now). Co-authored-by: Natalie Carey <natalie.carey@digital.cabinet-office.gov.uk> Co-authored-by: Joe Lanman <joe.lanman@digital.cabinet-office.gov.uk> Co-authored-by: Laurence de Bruxelles <laurence.debruxelles@digital.cabinet-office.gov.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have released v12.0.2 which works on M1 Macs
The text was updated successfully, but these errors were encountered: