Please support args.output for dbPath

[rottmann]

From hexo/lib/hexo/index.js

  // If `output` is provided, use that as the
  // root for saving the db. Otherwise default to `base`.
  const dbPath = args.output || base;

you can access it with hexo.env.args.output

[tea3]

@rottmann
It seems to be ok if change the following places, but I do not know how to use output. Please tell me how to use the detail.
https://github.com/tea3/hexo-include-markdown/blob/master/lib/orverwriteCache.js#L19

[rottmann]

It seems that output is an undocumented feature of hexo. If hexo is called with --output dirname/ dbPath uses output to store the db.json and not base-path.

[tea3]

@rottmann

I tried to use --output option, the path of the site changed but the path of db.json did not change. It does not seem to affect this plugins, but is recognition incorrect ?

$ hexo clean
$ hexo --output test/ s

enviroment

• node.js v9.4.0
• hexo 3.4.4

changed:

• localhost:4000/ → loaclhost:4000/test/

---

If the option change the path of db.json , I think that it will work if you change the code as follows.

https://github.com/tea3/hexo-include-markdown/blob/master/lib/orverwriteCache.js#L19

let dbPath    = !hexo.env.args.output ? path.join( process.env.PWD || process.cwd() , "db.json" ) : path.join( process.env.PWD || process.cwd() , hexo.env.args.output , "db.json" )

https://github.com/tea3/hexo-include-markdown/blob/master/lib/orverwriteCache.js#L144

let dbPath    = !res[1].hexo.env.args.output ? path.join( process.env.PWD || process.cwd() , "db.json" ) : path.join( process.env.PWD || process.cwd() , res[1].hexo.env.args.output , "db.json" )