You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2018. It is now read-only.
Run npm install and let it create package-lock.json
Delete contents of node_modules
Run npm install and see the following error
> elm@0.18.0 install /Users/XXX/XXX/node_modules/elm
> node install.js
Unfortunately, there are currently no Elm Platform binaries available for your operating system and architecture.
If you would like to build Elm from source, there are instructions at https://github.com/elm-lang/elm-platform#build-from-source
Fix was for me to delete and recreate package-lock.json by running npm install one more time. It worked and the diff is
My recommendation to the elm team would be to show the URL that was being downloaded in install.js as it incorrectly assembles the URL from faulty NPM data. I seriously thought that the platform indication was broken (and therefore causing a 404), but really it was NPM screwing up and giving wrong version information. But seeing the borked up URL string would have immediately told me that something is wrong with NPM.
The text was updated successfully, but these errors were encountered:
Giving an error message of "there are no npm binaries available for your operating system and architecture" with the Elm version included, e.g. "there are no Elm 0.18 binaries available..." would have helped identify the root of the problem here.
Disregarding any leading "https://registry.npmjs.org/elm/-/elm-" and trailing ".tgz" when parsing the version string would have prevented the bug in the first place.
npm install
with an old npm version.npm install
and let it createpackage-lock.json
node_modules
npm install
and see the following errorFix was for me to delete and recreate
package-lock.json
by runningnpm install
one more time. It worked and the diff isMy recommendation to the elm team would be to show the URL that was being downloaded in
install.js
as it incorrectly assembles the URL from faulty NPM data. I seriously thought that the platform indication was broken (and therefore causing a404
), but really it was NPM screwing up and giving wrong version information. But seeing the borked up URL string would have immediately told me that something is wrong with NPM.The text was updated successfully, but these errors were encountered: