Don't recommend installing typescript package globally in README #53209
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
typescript-bot
added
Author: Team
For Uncommitted Bug
|
I recall noticing this a few months back and wondered why it would recommend installing globally when pretty much everyone has strongly recommended against globally installing anything for basically forever. |
DanielRosenwasser
approved these changes
Mar 13, 2023
|
Globals are pretty nice for beginners - but it's really unclear what being a beginner means in the context of Node.js where there's such an expectation that you'll use a Also, npx didn't exist until a few years back. |
|
Yeah, besides this PR, we could just say to use |
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.
Saw this pop up in Discord today; I don't think installing the typescript package globally is a good idea at all these days (maybe no days).
Instead recommend installing it into the current package and as a dev dep.