Strange bug with symlinked next dir
#1062
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
1v9
approved these changes
Aug 5, 2019
|
Merge? |
|
Maybe someone will find better variant with path ( |
|
@theme-next/next so, if not exists any better suggestions for now, need to merge it. |
tongluyang
pushed a commit
to tongluyang/hexo-theme-next
that referenced
this pull request
Nov 19, 2019
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.
Fix for strange bug if
nextdirectory will be placed under symlink intheme→ Error: Cannot find module 'lodash/merge'. Releated to #1043.Steps to reproduce
hexo/themesnextphysical directory somewhere else, for example/home/usernamethemesdir:ln -s /home/username/next hexo/themes/next-symlinkAnd get something like that: