Skip to content

Conversation

curbengh
Copy link
Contributor

  • Others (Update, fix, translation, etc...)

New requirement introduced by hexojs/hexo#3778.

@curbengh curbengh added this to the v4.1.0 milestone Oct 22, 2019
@SukkaW
Copy link
Member

SukkaW commented Oct 23, 2019

IMHO, maybe we can address hexojs/hexo#3789 in this PR.

| Hexo version | Required Node.js version |
|:---:|:---:|
| > 4.1.x | >= 8.10 |
| 4.0.x | >= 8.6 |
| 3.3.x - 3.9.x | >= 6.9 |
| 3.2.x - 3.3.x | >= 0.12 |
| 3.0.x - 3.1.x | >= 0.10 or iojs |
| 0.0.1 - 2.8.x | >= 0.10 |
Hexo version Required Node.js version
> 4.1.x >= 8.10
4.0.x >= 8.6
3.3.x - 3.9.x >= 6.9
3.2.x - 3.3.x >= 0.12
3.0.x - 3.1.x >= 0.10 or iojs
0.0.1 - 2.8.x >= 0.10

The required Node.js version came from history of .travis.yml & package.json

@yoshinorin
Copy link
Member

yoshinorin commented Oct 24, 2019

I have already commented at hexojs/hexo#3789 (comment)
I agree with add Node.js compatibility doc to website.

IMHO, should avoid using a sign of inequality (like >=, >).

My understanding, these versioning specifications are used in npm, php composer, ruby gem (I don't know any more).

But, hexo user's programming background may be various. So, I think they are possibility that they can not understand what is mean >=.

@curbengh curbengh marked this pull request as ready for review December 6, 2019 00:48
@curbengh curbengh merged commit b779ea3 into hexojs:master Dec 10, 2019
@curbengh curbengh deleted the node-8.10 branch December 10, 2019 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants