move 'react-syntax-highlighter' to devDependencies#36
Open
mikaello wants to merge 1 commit intoupmostly:masterfrom
Open
move 'react-syntax-highlighter' to devDependencies#36mikaello wants to merge 1 commit intoupmostly:masterfrom
mikaello wants to merge 1 commit intoupmostly:masterfrom
Conversation
Using command: npm install react-syntax-highlighter@10.2.1 --save-dev
Contributor
|
Fantastic, @mikaello ! I'll merge this in now. |
|
@jcrowson gentle bump :) I guess this would fix the security warning for highlight.js |
This file contains hidden or 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
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.
Using command: npm install react-syntax-highlighter@10.2.1 --save-dev
Sorry for the mess in #33, I'll keep this branch clean :-)
(and if you're interested in any of the features I have implemented in my own fork (http://github.com/mikaello/modali), I'll be more than happy to prepare PR-s for those of interest).
Resolving issue #28