-
Notifications
You must be signed in to change notification settings - Fork 8
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
Don't use the versions file for tools installed via NPM #23
Comments
This function decides whether to fetch an exact version of a tool (because the user specified an exact version) or to look up the latest version in the versions file: setup-purescript/src/Setup/BuildPlan.purs Lines 54 to 80 in 915bfb6
However, if the setup-purescript/src/Setup/Data/Tool.purs Lines 78 to 80 in 915bfb6
...then we should skip the versions file altogether and just NPM install the tool at its latest version according to NPM: setup-purescript/src/Setup/Data/Tool.purs Lines 94 to 148 in 915bfb6
Currently that only covers |
Does something like this (#24) make sense as a possible fix? |
The versions file exists to avoid rate limits imposed by GitHub when getting the latest release for various tools via the GitHub API. However, if a user specifies they want the latest tool and the tool is installed via NPM, then we should skip the versions file and just NPM install the latest -- we don't get rate limited on that.
The text was updated successfully, but these errors were encountered: