Suggestion: Why not use npm to manage and record theme-next plugins?

[YunYouJun]

Suggestion

I find theme-next has some plugins(like theme-next-pace).

If I want to install this module, I have to use git clone to clone it in my folder.
Why not use npm to record these plugins? And then we can install it together just by npm install.

If there are any special reasons, can I know it?

I agree and want to create new issue

• Yes, I was on Hexo Docs page, especially on Templates, Variables, Helpers and Troubleshooting.
• Yes, I was on NexT Documentation Site.
• And yes, I already searched for current issues and this is not help to me.

---

[zhangyunhai210]

Npm is a bad choice,especially for users,not developers.of course,this is my point of view

[ivan-nginx]

Actually, i think about this. But NPM provide installs/updates for npm modules (e.g. node_modules dir). And NexT — is theme, which placed under generated Hexo's blog, inside blog/themes directory. So, i think there is no reason to add NexT into NPM; especially NPM at most cases work with JS files, but NexT work with mixed JS / CSS / SWIG files.

But, you are right and i see your vision: need to create something like autoupdate option to easy-way update/install NexT and all plugins to it.

[YunYouJun]

@ivan-nginx Thanks for your explanation. Looking forward to the realization of this function.

[ivan-nginx]

Added in NexT 7.0 Roadmap as Console reminder if new version released [autoupdate option] (#318).

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. It is possible issue was solved or at least outdated. Feel free to open new for related bugs.

[stevenjoezhang]

See: https://github.com/theme-next/awesome-next