chore: add .tool-versions, update README #93
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
aidandenlinger
force-pushed
the
aidan/tooling
branch
from
1090da2 to
a061642
Compare
aidandenlinger
force-pushed
the
aidan/tooling
branch
from
a061642 to
58cb8c1
Compare
aidandenlinger
changed the title
node version
aidandenlinger
force-pushed
the
aidan/tooling
branch
from
58cb8c1 to
d8a6ae9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some final housekeeping to make sure we can reproduce our dev environment in the future. If we want to show this project off but future
nodeupdates break this project, we want to know what version ofnodewe were using during development (in this instance, 19) to go back to a stable environment.Just as
package.jsontracks what versions of packages we're using, a.tool-versionsfile tracks what versions of compilers/tools are being used for the project. You can use it to manually check and download the required versions, but it can also be a configuration file used by the runtime configuration tool asdf, its rust clone rtx, or any other asdf compatible tool to automatically download/manage these dependencies.This also unpins node 19.7, as 19.8.1 was released to fix nodejs/node#47096 (which is the issue we were running into).
Finally, added a link to our latest deployment and picture of the homepage so that the README has everything.