8000 Enhancement: Publish typescript-eslint to JSR · Issue #11090 · typescript-eslint/typescript-eslint · GitHub
[go: up one dir, main page]
Skip to content

Enhancement: Publish typescript-eslint to JSR #11090

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.

Sign up for GitHub

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

Jump to bottom
Open
4 tasks done
cylewaitforit opened this issue Apr 19, 2025 · 4 comments
Open
4 tasks done

Enhancement: Publish typescript-eslint to JSR #11090

cylewaitforit opened this issue Apr 19, 2025 · 4 comments
Labels
accepting prs Go ahead, send a pull request that resolves this issue enhancement New feature or request

Comments

@cylewaitforit
Copy link

Before You File a Proposal Please Confirm You Have Done The Following...

Relevant Package

typescript-eslint

My proposal is suitable for this project

  • I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Description

It would be nice to see typescript-eslint also published to JSR.

Additional Info

Some of the @eslint scoped packages have started publishing to JSR.
@cylewaitforit cylewaitforit added enhancement New feature or request triage Waiting for team members to take a look labels Apr 19, 2025
@JoshuaKGoldberg
Copy link
Member

👍 I'm in favor, and don't see any strong reason not to.

@bradzacher
Copy link
Member

The main reason I haven't bothered pursuing this is really just cos there's a whole piece of auth management for this that we'd need to setup, and the desire from the people to use JSR hasn't been there yet (this is the first request for it thus far).

@cylewaitforit
Copy link
Author

@bradzacher That totally makes sense. I think, like most things, early on it had the chicken and egg problem. Not enough packages there for users to start using it, not enough users using it for packages to publish there.

My gut is that the flywheel has started spinning, especially with the pnpm and yarn support news this week but maybe I've just found the echo chamber. I couldn't point to any definitive numbers to support it.

@JoshuaKGoldberg JoshuaKGoldberg added accepting prs Go ahead, send a pull request that resolves this issue and removed triage Waiting for team members to take a look labels May 7, 2025
@JoshuaKGoldberg
Copy link
Member

This will probably need some assistance from us on the team for tokens or permissions or whatnot. But it would be lovely if someone could help get it started. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepting prs Go ahead, send a pull request that resolves this issue enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@JoshuaKGoldberg @bradzacher @cylewaitforit
0