fix: no such file or directory error caused by sitemap.xml not includ…

[yoshinorin]

…ed package

Why?

We specified which file includes or not in #49 and we decided includes index.js & lib directory.
But, this package must include sitemap.xml. If it does not include below error occurs.

INFO  Start processing
FATAL Something's wrong. Maybe you can find the solution here: https://hexo.io/docs/troubleshooting.html
Error: ENOENT: no such file or directory, open 'C:\Users\N.Yoshinori\site\node_modules\hexo-generator-sitemap\sitemap.xml'
    at Object.openSync (fs.js:431:3)
    at Object.readFileSync (fs.js:333:35)
    at module.exports (C:\Users\N.Yoshinori\site\_main\node_modules\hexo-generator-sitemap\lib\template.js:21:37)
    at Hexo.module.exports (C:\Users\N.Yoshinori\site\_main\node_modules\hexo-generator-sitemap\lib\generator.js:27:13)
    at Hexo.tryCatcher (C:\Users\N.Yoshinori\site\\_main\node_modules\bluebird\js\release\util.js:16:23)
    at Hexo.<anonymous> (C:\Users\N.Yoshinori\site\_main\node_modules\bluebird\js\release\method.js:15:3

Sorry, I made a mistake when review. this error is my fault...

@weyusi
Would you review it?

[coveralls]

Coverage remained the same at 100.0% when pulling a7dfa45 on YoshinoriN:fix-sitemapxml-not-exist into 77bf38b on hexojs:master.

[coveralls]

Coverage remained the same at 100.0% when pulling a7dfa45 on YoshinoriN:fix-sitemapxml-not-exist into 77bf38b on hexojs:master.

[coveralls]

Coverage remained the same at 100.0% when pulling a7dfa45 on YoshinoriN:fix-sitemapxml-not-exist into 77bf38b on hexojs:master.

[curbengh]

yeah, I just realized it too, I should've tested npm publish --dry-run before PR.
please merge.

[yoshinorin]

Hmm... It seems to require @hexojs/core teams review...

@hexojs/core
Would you someone check it?

[tcrowe]

Thank you, @yoshinorin 👍

[tcrowe]

Do we need to bump the version number in this PR? Maybe a different one?

[tcrowe]

Thank you also, @weyusi

[yoshinorin]

Do we need to bump the version number in this PR? Maybe a different one?

No. This is a regression bug.
Thanks @tcrowe :)