Error trying to install node-sass@4.12.0 on MacOS Catalina

[afragen]

In the package.json of develop.svn.wordpress.org lists "node-sass": "~4.12.0" in devDependencies.

After git clone git://develop.git.wordpress.org/ /public and then running npm install on my Mac from the proper directory I get the following error. I'm running Mac OS Catalina FWIW.

Cannot download "​https://github.com/sass/node-sass/releases/download/v4.12.0/darwin-x64-79_binding.node":
HTTP error 404 Not Found

I don't no why it's looking for this particular package darwin-x64-79_binding.node but it doesn't exist on GitHub.

Updating the package.json to use "node-sass": "~4.13.0" seems to work.

[desrosj]

@afragen which version of Node are you running? My hunch is that you are running Node 13, which does not seem to be supported in 4.12.0.

The darwin-x64-79_binding.node is the packaged asset for the release corresponding to the environment you are running. Looks like this specific one ​is not present for 4.12.0, but ​is for 4.13.0, so that's likely the issue.

Looking at the release notes for v4.13.0, it seems that the only changes made not related to Node 13 support are for documentation and Travis configuration. I think bumping the version for this should be fine, but it should also be updated in the Gutenberg repository.

Until this is deemed OK and updated in trunk/Gutenberg, you can use ​NVM to switch versions based on .nvmrc files in directories for the best experience. Running nvm use will switch to the version recommended there.

[afragen]

@desrosj I am running node v12.13.1

Which version are you suggesting I switch to?

[UmeshSingla]

@desrosj Tested the build with node v12.16.1, npm install worked fine for me with the following message.

"Binary found at /Users/umeshkumar/Documents/umesh/tests/wordpress/node_modules/node-sass/vendor/darwin-x64-72/binding.node
Testing binary
Binary is fine"

[SergeyBiryukov]

Updating the package.json to use "node-sass": "~4.13.0" seems to work.

node-sass was updated to ~4.13.1 in [47404] / #49547.

Closing as fixed, feel free to reopen and move to a future release if there's still an issue.