Release: use npm publish

[RobinTail]

Lastest release failed to be published:
https://github.com/import-js/eslint-import-resolver-typescript/actions/runs/9928981640/job/27425949199

Based on this thread
https://stackoverflow.com/questions/64589655/package-is-not-publishing-to-npm-not-in-the-npm-registry

npm publish might work

[changeset-bot]

⚠️ No Changeset found

Latest commit: 234dca4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[RobinTail]

@SukkaW || @JounQin , please review

[RobinTail]

@SukkaW || @JounQin , please review

[SukkaW]

IMHO I don't see switching to npm publish would help in this case. Would you mind explaining any difference between yarn release and npm publish here?

[RobinTail]

Would you mind explaining any difference

I just know that npm works for publishing into the NPM registry.
I always use npm publish myself despite using yarn for everything else.
The link in the description proves that yarn release may cause unexplainable issues.
Since this is exactly what we're currently dealing with ("package is not in the registry" error, while it is clearly there), I'm suggesting to give it a try.
Can not explain it better. But if it will work — we would fix the publishing issue. If not — it's easy to revert, @SukkaW

[SukkaW]

The link in the description proves that yarn release may cause unexplainable issues.

The StackOverflow question doesn't mention yarn anywhere other than description in the example package.json:

On the other hand, yarn release is not a yarn built-in command. It is a project-wide custom script:

eslint-import-resolver-typescript/package.json

Line 52 in a4c6c78

"release": "changeset publish",

Closing the PR.

[RobinTail]

Is there a plan to do something better than this and fix the release, @SukkaW ?