fix: plugin loading conflict with @vercel/nft

[SukkaW]

What does it do?

Hexo uses browserify's resolve to resolve a path of a plugin by default, which is incompatible with @vercel/nft. See also: vercel/nft#257

So we use Node.js's built-in require.resolve by default (which is compatible with @vercel/nft), fallback to resolve.sync only when the module is not found (or other errors).

Since there are no other significant behavior differences (from hexo's usage) between resolve.sync and require.resolve, we should drop resolve from dependency in the future.

How to test

git clone -b fix-plugin-resolve https://github.com/sukkaw/hexo.git
cd hexo
npm install
npm test

Screenshots

Pull request tasks

• Add test cases for the changes.
• Passed the CI test.

[coveralls]

Coverage decreased (-0.05%) to 98.096% when pulling 83ec33f on SukkaW:fix-plugin-resolve into 9d064d2 on hexojs:master.

[tomap]

I approve, but unable to fully understand this change and it's potential impacts

[SukkaW]

I approve, but unable to fully understand this change and its potential impacts

The API require.resolve is introduced in Node.js since 0.3.0, however it doesn't support limit scope resolving (only search dependency in the given directories' node_modules, in our case is user's hexo folder) back then. That's probably why package resolve (made by browserify) is used (it provides a base_dir option).

And since Node.js 8.9.0, require.resolve accepted the second argument, which enables to only search under specific given paths.

It shouldn't have any impact at all. And in case there is any, I still use the old resolve package as a fallback, trying to avoid a breaking change.