-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
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
Properly support Apple Silicon (M1) devices #41
Comments
Originally posted by @DeMoorJasper in #33
|
I think node still doesn't have official Apple Silicon builds? |
@devongovett I don't think so, it's probably related to this issue parcel-bundler/parcel#5046 instead as Apple keeps "improving" their security |
Correct, this is an arm node built from 15.3.0 which includes a patch from upstream V8 solving a previously blocking issue Node Merged V8 apple arm macro: https://chromium-review.googlesource.com/c/v8/v8/+/2517689 Node does not, as of the time of this writing, provide officially supported builds of Node for M1 Macs. Also just to clarify I don't want to sound like I'm demanding an open source project support brand new hardware immediately. I know things take time and effort, both of which have a corresponding monetary value and that it is completely unreasonable of anyone to ask an OSS project to support 2 week old hardware immediately. To give some context on things I've tried, I have gatekeeper disabled, and signed the binary by hand myself with
|
@WA9ACE Are you sure this is related to parcel-bundler/parcel#5046 and therefore the codesign situation? If you get the error described in #33, then it's probably related to ARM itself. |
Just tried on my M1 Macbook I just got and it works fine when using Rosetta, which is probably still the recommended way of running NodeJS at this point? |
Resolved by #52 |
Ensure this package also runs on M1 Macs, besides this also build binaries for these devices and publish them in a new release.
Originally posted by @WA9ACE in #33 (comment)
TODO:
The text was updated successfully, but these errors were encountered: