New version needs to be pushed to npm

[dsolovay]

npm still lists version 0.1.0 as current: https://www.npmjs.com/package/hexo-generator-alias

0.1.0 is the latest of 2 releases

Please issue an npm publish command to update npm to the current version.
https://docs.npmjs.com/getting-started/publishing-npm-packages

[Xuanwo]

@tommy351

[laurentkempe]

You can also install it directly from github repo with the following command

npm install git+https://github.com/hexojs/hexo-generator-alias.git --save

And then it works with Hexo 3.0

[curbengh]

New version needs to be published for hexo@3 compatibility.
Once this issue is closed, #1 and #2 can be closed too.

[tomap]

I publushed a pre release
https://www.npmjs.com/package/hexo-generator-alias/v/1.0.0-rc1
Anyone wants to validate?

[curbengh]

I'll do it.
If there is no issue, release v1 after hexo v4 is published.

[tomap]

Why after?

[curbengh]

Perhaps we should move the discussion about plugin release to hexojs/hexo#3508, https://github.com/orgs/hexojs/teams/core/discussions/5 or hexojs/hexo#3630. My understanding is that plugins (which drops node 6) should be released after hexo@4 or at least together.

[curbengh]

I publushed a pre release
https://www.npmjs.com/package/hexo-generator-alias/v/1.0.0-rc1
Anyone wants to validate?

I can confirm it works. But before v1.0 stable release, I want to update the readme to clarify the function.