Update README.md for #1256

[kirill-konshin]

No description provided.

[coveralls]

Coverage decreased (-0.1%) to 93.971% when pulling 784b602 on kirill-konshin:master into 9bac44e on benmosher:master.

[coveralls]

Coverage increased (+3.2%) to 97.313% when pulling 2a903db on kirill-konshin:master into 9bac44e on benmosher:master.

[coveralls]

Coverage increased (+3.2%) to 97.313% when pulling 2a903db on kirill-konshin:master into 9bac44e on benmosher:master.

[benmosher]

Actually two things:

• might be good to include a note about installing the typescript parser since it is not an included dependency
• should it be @eslint/typescript-parser? Isn’t that the current package name?

[kirill-konshin]

You're right! In fact, the recommended config should also be updated to this new naming. Hold on ) I will push an update.

[kirill-konshin]

Done. Pls squash before merge )))

[benmosher]

That is my bad for totally failing to remember the right package name off the top of my head 😳

I double-checked just now and updated both to the actual npm name. Thanks for this!

[kirill-konshin]

Lol, it happens ) good that it was captured. What's the release ETA? Considering that rename happened just recently it's important to be up to date... NPM version now contains old package...

[marcneander]

Would love a new release with this 👍

[EvertEt]

Any idea about the ETA for a new version including @eslint/typescript-parser?

[kirill-konshin]

Are you guys collecting some additional changes before releasing this? Are there any roadblocks?

[teoxoy]

I would like to see a new version with this too! 👍

[kirill-konshin]

Any news regarding the release? Last was on Jan 29... Also there's a fix for #1282 merged this morning...

[mcmar]

@ljharb This has been in the README for 3 months now, but it still hasn't been released to npm. As a result, anyone who follows the README on github is getting broken builds.
Reported here: #1285
Can you please do a release?

[ljharb]

That’s always a risk; one should check the readme for the latest released tag, not master.

A release will happen when time permits; further commenting doesn’t make that happen any faster.

[kirill-konshin]

Just to make it clear, is there any particular reason that holds off the release other than lack of time to do it? Is there any help needed?

[ljharb]

That’s pretty much it; it’s not something that i think can be helped at this time, unfortunately.

[kirill-konshin]

@ljharb do you mind considering to add more collaborators who can release? No offense, but 2+ months since last release is a lot. Looks like tests are passing but the build is failing, is this the issue that holds release? Are there any other pre-release checks that have to be done?