Remove unnecessary files after hexo generate

[1v9]

No description provided.

[stevenjoezhang]

In fact, there may be a lot of unnecessary files in source/lib, but they are hard to remove...

[jiangtj]

If cdn setted, may need remove...

[1v9]

Only touch those files belong to NexT, not plugins installed to source/lib.

[1v9]

Sorry guys it's truly difficult for me 😂.

Hexo has config.ignore which could perfectly ignore directories, it's different from config.exclude and config.skip_render. You know we merge config on generateBefore and hexo also has built-in merge config functions so it may be complicated.

Then I tried to operate files by hexo-fs on a lot of filters or events, failed again. Only deployBefore is easy to configure but too restrictive. Need to find a good way to handle hexo g, hexo s, hexo d.

hexo.route used by this PR only supports string so I listed all files.

Both hexo.route and config.ignore solve the problem, but one is not very beautiful and the other is a bit complicated.

[jiangtj]

Both hexo.route and config.ignore solve the problem, but one is not very beautiful and the other is a bit complicated.

hexo.route is enough, it can remove the file with the specified path before the file is generated.

hexo.route used by this PR only supports string so I listed all files.

Path can not be a String?

Hexo has config.ignore which could perfectly ignore directorie

Are you sure that we can get the configuration of the theme before hexo calls config.ignore?

[1v9]

@stevenjoezhang @jiangtj Have a look?