Hexo compile time JS confusion Solutions

Prior to writing your own html page on GitHub blog, source documents in a folder in the root directory hexo put their js document, every time hexo gafter, pubic document folder js document to confusion, inconsistent with their actual js.

solution:

1. hexo gAfter compiling modified public documents folder, the document covering their js js document compiled after hexo. Or hexo dsubmitting to GitHub GitHub online directly to modify js documents.
2. Js blog in reference to the use of the form of the chain. As the js file uploads seven cattle cloud , references js on seven cattle cloud.
3. Skip hexo rendering [Recommended].
   Hexo 3.0 using the following:
   Add README.md document or html file in your home directory.
   Hexo 3.0 above support:
   Modify skip_render configuration parameters _config.yml documents under Hexo home directory.

. 1 2 . 3 . 4 . 5 . 6 . 7 . 8 . 9 10 . 11 large column   JS confusion when Hexo solution compiled pre>

skip_render: "test.html" skip_render: test/* skip_render: test/*.md skip_render: test/** skip_render: # multiple documents, folders, and other cases - the Test / * - . the Test / * HTML

Note: If no effect after modifying the configuration, the first execution hexo cleanafter the implementation of hexo grecompilation

Original >>
HEXO Solutions to Common Problems