Update parse5 to the latest version 🚀 #14
Merged
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.
Version 3.0.3 of parse5 was just published.
The version 3.0.3 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of parse5.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v3.0.3Changelog: http://inikulin.github.io/parse5/#3-0-3
Commits
The new version differs by 14 commits.
723d782v3.0.38d38fdaMerge pull request #212 from gfx/patch-189e6b04loosen the dependency version of @types/nodefee4018Merge pull request #207 from inikulin/escape-zero-char67f0099Escape NUL character in feedback tests2aff591Merge pull request #198 from stevenvachon/master02d9feeImprove location info documentationae7b8a0Merge pull request #196 from stevenvachon/masterd0769dbFix empty stream parsing with ParserStream (closes #195)fabc6d8Bring no-trailing-spaces eslint rule backd9c0881Merge pull request #186 from HTMLParseErrorWG/mastered932c8Calculate offset in position trackerc7f1193Refactor location info parser mixin549218bRefactor location info tokenizer mixinSee the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴