Skip to content

Don't recommend installing typescript package globally in README #53209

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

Merged
merged 1 commit into from
Mar 13, 2023

Conversation

jakebailey
Copy link
Member

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.

@typescript-bot typescript-bot added Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug labels Mar 11, 2023
@fatcerberus
Copy link

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.

@jakebailey jakebailey merged commit e1488fe into microsoft:main Mar 13, 2023
@jakebailey jakebailey deleted the readme-install-no-global branch March 13, 2023 20:08
@DanielRosenwasser
Copy link
Member

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 package.json with dependnecies.

Also, npx didn't exist until a few years back.

@jakebailey
Copy link
Member Author

Yeah, besides this PR, we could just say to use npx if there's any doubt. That'll always do the right thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Author: Team For Uncommitted Bug PR for untriaged, rejected, closed or missing bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants