Should hexo-cli package bundles with hexo-starter and hexo-theme-landscape? about hexo-cli HOT 7 CLOSED

I agree with the first approach: the installation of Hexo only requires npm, while git is optional.

Besides, hexo-theme-landscape can be installed through npm, which will reduce the number of git submodules.
The package was registered on npm a few years ago: https://www.npmjs.com/package/hexo-theme-landscape
I have contacted npm support and obtained the ownership of the package.

from hexo-cli.

the installation of Hexo only requires npm, while git is optional.

hexo currently mentions git is required though and hexo init defaults to git-cloning hexo-starter. but really, using hexo actually doesn't need git, indeed many themes show git clone in their installation guide, however users can use github's "download zip" as well (we can mention this in docs); and of course new themes are being npm-published.

I can also imagine that the installation of Git Windows to be a bit intimidating for newcomers (git bash, PATH, commit unix-style, credential helper, etc).

I have contacted npm support and obtained the ownership of the package.

🎉

from hexo-cli.

I also noticed our past effort in version-controlling the "assets/" folder (see 4.1.0 and 3.1.0) have no effect at all because hexo init defaults to cloning latest master of hexo-starter, e.g. hexo-cli v3 installs hexo v5.

Currently the "assets/" submodule is only used for unit testing.

from hexo-cli.

@curbengh How could I transfer the hexo-theme-landscape package to hexojs organization (https://www.npmjs.com/org/hexojs) on npm? Thanks

See also
hexojs/hexo-theme-landscape#173
hexojs/hexo-starter#45

from hexo-cli.

I believe @NoahDragon is the admin of hexojs npm org, so just add him abnerchou <[email protected]> as owner and he can do the rest.

$ npm owner ls hexo
abnerchou <[email protected]>
curben <[email protected]>
ertrzyiks <[email protected]>
hexobot <[email protected]>
jlhwung <[email protected]>
tomap <[email protected]>
tommy351 <[email protected]>
yoshinorin <[email protected]>

from hexo-cli.

We could also point to a GitHub repo in the meantime

from hexo-cli.

hexo-starter has been updated: hexojs/hexo-starter#45

Now you can use git submodule to update the assets folder and publish it with hexo-cli on npm

See also hexojs/hexo#4569

from hexo-cli.