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.
I think we are ready to release v1.0.0 🎉
This release is meant to be non-breaking for most users so they can get onto a stable release easily.
The only users that will need to change their code are users who are extending the lexer or parser currently. Those users should move to extending the
tokenizer
andrenderer
with the newmarked.use()
function.After v1.0.0 is released we can look into moving some of the current options into extensions in future releases (as well as making marked more spec compliant). We can maintain some extensions under the @markedjs group but hopefully the community will also follow with some extensions of their own.
Release Notes
Breaking changes
marked.lexer
output Inline tokens #1627Tokenizer
to allow extending token creation Tokenizer #1637Features
marked.use()
method to extend options marked.use #1646Fixes
_
) breaks links containing underscores fix: Italics modifier (_) breaks links containing underscores #1641Docs
CI
Publisher
$ npm version
has been run.master
with correct version number.$ npm publish
has been run.Note: If merges to
master
occur after submitting this PR and before running$ npm pubish
you should be able toupstream/master
(git pull upstream master
) into the branch holding this version,$ npm run build
to regenerate themin
file, andCommitter
In most cases, this should be someone different than the publisher.
package.json
has been updated (see PUBLISHING.md).marked.min.js
has been updated; or,