forked from hexojs/hexo
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update from original. #1
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* increased test coverage for console plugin * removed unwanted imports * fixed linting error
* 删除 jsfiddle 网址前面的 http 限制 * 删除 jsfiddle 的 test
Add gitter icon.
* multiconfig working * rename and fix warning * switched to hexo-log * passing context to multiconfig for slilencing capability * added tests * formatting and undoing random change at line 328 * fixed logging output testing * style error fixes... ✨
Add node 7
* fixed <meta name="keywords"> not generated * jscs passed * fixed test/open_graph.js * eslint pass
* yarn lock file * Fix post order bug where posts where ordered oldest to newest. Updated tests to check for every posts prev and next properties. * gitignore yarn.lock
…y has parameter (#2274)
* Add support for npm scoped packages as plugins * load_plugin: add test for scoped package
If first 200 characters have new line(s), Hexo will generate something like this: ```html <meta name="description" content="We’ve continuously been hearing for a couple of years now that Samsung is working on foldable smartphones. The company has a plethora of patents to its name that detail some of the technology"> ``` This PR fix this little problem.
* Added backers and sponsors on the README * Added call to donate after npm install
….tags or config.keywords (#2535) * support keywords from page.keywords, page.tag or theme.keywords * fix code style error * change to config.keywords * no escape for image * fix escape for description * add test case and fix bug * fix code style
When using a custom server, I would like to store only the output of hexo's build process, and no extra dependencies, and the way I can do that is by storing the plugins in devDep and running npm install --production to get the server dependencies.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.