Repository navigation
Support macOS Big Sur (10.16 / 11.0) #34043
Description
Activity
Related: nodejs/TSC#886
- changed the title
[-]Support macOS Big Sur (10.16)[/-][+]Support macOS Big Sur (10.16 / 11.0)[/+]on Jun 24, 2020 Installing Node 14.4.0 from Homebrew worked just fine on my MacBook. Also, I have the enrollment command, but i'm not sure if it'd be safe to post here.
I installed the latest xcode tools and node now installs
Reacted by Matt Pilott, Niko, ariana02880 and Ramon-Limma
@mcollina: Yeah, but I'm not sure what we're going to do with that. I don't think we want to be installing betas on our CI machines, that could get messy. I'm not sacrificing my machine for this upgrade, I only just bit the Catalina bullet and don't exactly trust Apple's recent track record on OS quality.
@AshCripps did we set up those MacMinis with VMWare Fusion? Is it worth the hassle installing and playing around with it? If you don't already have access to our Apple Developer team we should get you that, I think as a member of the team everyone gets access to this.
I know its very early days, but currently node fails to install on macOS 10.16 installing via brew
@matt3224 I think it would be best if you tried installing it directly. There's multiple steps between Node.js and you using Homebrew that could cause problems, and we're only responsible for a few of them. Just clone this repo, (optional: check out one of the stable branches, 14.x perhaps), run
./configure && make -j8 installand tell us if and how it fails.Reacted by Matteo Collina, Jesse Youngblood and Jiawen Geng@rvagg Those macminis were set up with fusion so if you can get me an iso (or whatever apple gives you) I can set up a test machine. not 100% sure if it will require an update the the vmware itself and we may have to sacrifice a test machine (we have like 5 in total iirc so no issue).
I dont know if I have access to the developer team I never checked.
I don't know if it's worth your time or the sacrifice of a CI machine just to test things out this early. During these beta periods we normally rely on users submitting fixes or at least errors with enough information that we can figure it out. We're super early with Big Sur so I'm inclined to recommend we not spin our wheels this early. I'll get you set up in our Apple Developer team though so you can make a judgement for yourself, perhaps you're interested enough for personal reasons to have a poke at it!
We've got some time anyway VMware Fusion isn't releasing a tech preview with big Sur support until next month anyway so we can't install it anywhere
I'd be happy to help, however I don't know any thing about the Node codebase,but the download on Apple's Dev site only downloads a tool which enables the current machine upgrading to Big Sur. I don't know if you can download an ISO/DMG from Apple's site, if you can't i could possibly zip up a install media image?
14.7.0 does not install though, just FYI
5 remaining items
For anyone who's currently trying to use Node on a DTK, it should now work via brew - just update and install
- added a commit that references this issue
on Sep 1, 2020 - Reacted by Vlad, Harsh Bharvada, Mike Rudge, Eduardo Ludi, Marco Marques, Sayan Das, Jonathan Neal, Felix Alcala, Fowad and Tony SpataroReacted by Dave Sag, Jonathan Neal and Fowad
Sorry for pinging this old issue, but I didn't know how else to bring this to attention.
Recent RCs of Big Sur 11.2 broke node (on Apple Silicon at least), see #37061
My intention isn't to spam, but there hasn't been any acknowledgement in that thread that it is being looked into, and this is pretty serious as it completely blocks development (unless reverting to node 14 and rosetta).
Reacted by Jason Mellblom, Richard Boardman, Vini Katyal, fpeyret and Stephan Barrett
Is your feature request related to a problem? Please describe.
I know its very early days, but currently node fails to install on macOS 10.16 installing via brew
Describe the solution you'd like
For node to work on 10.16, which of course naturally it will be, closer to release
Describe alternatives you've considered
The only alternate solution is to not use 10.16, which is totally fine, no pressure!