Skip to content
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.

Consider using the tarball instead of the pkg installer for OS X #13

Open
evanlucas opened this issue Jul 1, 2016 · 5 comments
Open

Comments

@evanlucas
Copy link
Contributor

We have had a lot of issues with the pkg installer (especially when upgrading from v4 -> a version that contains npm 3) not fully replacing npm.

@Fishrock123
Copy link
Contributor

Yes please.

@mikeal
Copy link
Contributor

mikeal commented Jul 5, 2016

It takes considerably longer to compile the tarball and it requires that the dev tools and compiler are installed.

We should detect the npm issue and write some code that fixes it :)

@evanlucas
Copy link
Contributor Author

I was suggesting using the pre-compiled tarball for OS X.

We could use pkgutil and installer to determine which files to remove prior to installation, but that seems a bit messier to me

@MylesBorins
Copy link

+1 for pre compiled tarball... these can be grabbed just as easily as the pkg util... We will still have the issues from npm 2 -> npm 3 if we don't rimraf /usr/local/lib/node_modules/npm on install

An alternative would be to install using a folder schema similar to nvm, that way we never touch /usr/local

@soegaard
Copy link

I ran into a problem where the 10.16.0 installer wouldn't install on my mac.
Looking in the source of the installer, I found out that it just runs Apple's utility installer like this:

 installer -dumplog -pkg node-v10.16.0.pkg -target /

(I added -dumplog).

The tarball and/or pkg files can be found here:

 https://nodejs.org/dist/v10.16.0/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants