Publish v0.6.0 to NPM

[davecardwell]

I was keen to check out the fix for #329 (thank you!), but it looks like v0.6.0 was tagged but not published to NPM yet.

Please could you publish?

[veritem]

I'm having an issue with npm's authentication. Once I hear back from them, I'll for sure get this published and sorry for not adding this into release notes.

[davecardwell]

@veritem Thank you!

[rentalhost]

For now this worked for me:

"eslint-plugin-vitest": "github:veritem/eslint-plugin-vitest#semver:^0.6"

[CxRes]

Can you please start checking in ./dist to this or another repo while you do not have npm access?

Alternatively, publish it on jsr.io!

[lishaduck]

Can you please start checking in ./dist to this or another repo while you do not have npm access?

Please don't check in dist. Put it in another repo.

Alternatively, publish it on jsr.io!

That would be nice.

[erunion]

👋 any updates on this?

[veritem]

I haven't heard back from npm/gitHub support since June, and I don't know anyone who works there. still waiting...

[joel-daros]

If you haven’t received any answer in months I don’t think anyone will answer you anyway. In your position I’ll start thinking in creating another account and publish it as a different name.

[meduzen]

In your position I’ll start thinking in creating another account and publish it as a different name.

I second this. Last year I try to reach the support to help someone at work, we never received any answer.

[tianyingchun]

oh, just fork, and temporary publish "eslint-plugin-vitest-2": "^0.6.1" , wait you npm account

[Sparticuz]

Is there anything that can be done? There really isn't a way to use the latest version of this package right now.

[Stanzilla]

Agree, a new version would be very welcome, especially with the TSESLint peer dep fixed.

[meduzen]

oh, just fork, and temporary publish "eslint-plugin-vitest-2": "^0.6.1" , wait you npm account

That’s what @veritem did: https://www.npmjs.com/package/eslint-plugin-vitest-2

It works on my side (do not forget to add the -2 to your package.json and your ESLint config file.)

[veritem]

@meduzen that package does not belong to me.

[CxRes]

@meduzen It is Yingchun Tian @tianyingchun who is forked the package to https://www.npmjs.com/package/eslint-plugin-vitest-2 on npm. Given @veritem 's issues with their npm account, I think this is a reasonable stop-gap solution and gives us access to the latest version.

[veritem]

I have moved on guys!

npm install eslint-plugin-vitest-latest

open an issue if something breaks

[veritem]

We have a new home 🎉

npm install @vitest/eslint-plugin

[Sparticuz]

Woah, even better, congrats!

[tianyingchun]

My own project has switched to the new version and works fine，@hyperse/eslint-config-hyperse