v7.1.2

This release includes parse5 and parse5-parser-stream.

• Export ERR as ErrorCodes by @milahu in #704
• Properly handle CR when peeking by @fb55 in #715
• Add CJS build of parser-stream by @fb55 in #716

Full Changelog: v7.1.0...v7.1.2

v7.1.0

This release is only for the parse5 module.

What's Changed

• feat(parse5): use string types for node names by @43081j in #631
• fix(parser): Have </button> close <p> by @fb55 in #534
• docs: Fix small typo in code example by @cheeaun in #518
• Added coverage reporting by @fb55 in #515
• Improved code coverage by @fb55 in #517 and #547

New Contributors

• @cheeaun made their first contribution in #518

Full Changelog: v7.0.0...v7.1.0

v7.0.0

Welcome to parse5@7.0.0! ✨ This is a huge release with many changes, features and fixes.

From an organisational perspective, the most important change is that parse5 is now maintained by a team, consisting of James (@43081j), Titus (@wooorm) and me (@fb55). We come from three projects that rely on parse5 — namely Cheerio, rehype, and Lit.

We need your support to continue the project! If you care about parse5, please support us financially on OpenCollective.

Headlining features of this release are ES Modules, TypeScript, and performance improvements: 7.0.0 is 45% faster than 6.0.1 with default options, and 167% faster with location information enabled (for the bench/perf benchmark, on an M1 Mac). Version 7.0.0 is a revamp of every part of the library. There are too many changes to list them all here, so here is a high-level overview:

Breaking: ESM

All of parse5’s packages are now ECMAScript Modules. We are providing dual packages for parse5 and parse5-htmlparser2-tree-adapter for now (see #418 and #496).

To migrate, please read this Gist on how to update. Note that private internals are no longer available; instead, everything that you need should be imported from the main package.

Implemented by @43081j in #351

Breaking: TypeScript

The codebase has been ported to TypeScript. This helped uncover a number of subtle logic bugs, such as dc4e269, b4b5d4a, or a0aff95. TypeScript also helps us refactor with confidence and a lot of the changes in this release would have been much harder to do without it.

To migrate, please remove @types/parse5* as we now ship our own types.

Implemented by @fb55 in #362

Potentially breaking changes

• parse5 was caught up with the HTML spec, and parsing results might differ in edge-cases (#442, #451)
• The parse5-serializer-stream package was removed #481
  • To migrate, use the serialize function exported by parse5.
• The rewriting stream now splits very long text sections (#434) and doesn’t escape text in special tags anymore (#434). If you worked around these issues before, you might have to update your code.
• The htmlparser2 adapter now uses domhandler’s node interface (#327 by @TrySound)
  • The format of the tree nodes has changed slightly; eg. some previous properties are now getters and setters, and vice versa.

If you are using deep imports for any parts of the codebase, you will likely encounter some breakages:

Show internal changes

• The tokenizer now uses the state machine pattern from htmlparser2 5d7a780 (#362)
• The token queue was replaced with callbacks (#404, #405, #419)
• The OpenElementStack now uses callbacks #429
• Mixins were removed (as part of #362)
  • Location tracking now has a substantially lower overhead #402
• getNextToken was removed #461
• The parser’s _bootstrap method was removed #384
• We now drop chunks from the tokenizer right after they are emitted #432
• The serializer is no longer a class; instead, different serializer functions call on each other #383
• parse5 now uses the entities module for encoding and decoding entities, sharing maintenance & optimisation work with projects such as htmlparser2 (2b92054 (#362), #486)
  • entities adopted a variant of parse5’s approach of decoding entities. As a result, decoding performance is equivalent, while memory consumption is slightly lower.

Other changes

• minor add hooks for stack events to tree adapter interface #385
• minor add support for fragments in parse5-parser-stream #487
• minor add serializeOuter (like .outerHTML), scriptingEnabled option #383
• patch fix parsing of << in comments parsed wrongly as <! (#326)
• patch fix position of endTag for mixed-case foreign elements (#353)
• patch fix end position of html, body (#436)
• docs: parse5 has a new documentation website at parse5.js.org #443

New Contributors

Thanks @anko, @TrySound, @samouri, @alan-agius4, and @pmdartus!

Full Changelog: v6.0.1...v7.0.0

v6.0.1

• Fixed: Handling of self-closing <hr> tags (by @43081j).
• Fixed: Broken link in TreeAdapter document (GH #317) (by @ursm).
• Fixed: SAXParser example (GH #316) (by @mvasilkov).

v6.0.0

• Added (breaking): Tree adapter interface now has updateNodeSourceCodeLocation method which enables usage of custom location info formats (GH #314) (by @DMartens).

v5.1.1

• Fixed: Serialization of attributes in non-standard namespaces (by @Zirro).
• Fixed: Quirks and limited-quirks mode detection by doctype (by @squidfunk).

v5.1.0

• Fixed: Location info for text events in SAXParser and RewritingStream now contains
  correct endCol and endLine covering all concatenated raw tokens (GH #266).
• Fixed: SAXParser and RewritingStream now flush last buffered chunk when calling .end() with
  no parameters (GH #271).
• Updated (breaking): ParserStream, SAXParser and RewritingStream no longer assume that
  each binary chunk is a valid finished UTF-8 chunk, and instead accept only decoded strings (GH #269).

v5.0.0

Starting from this release parse5 functionality will be shipped in separate packages. With parse5 package contatining only basic functionality. Please, refer to the list of packages for more info.

• Updated (breaking): source code location now inserted by tree adapter, so tree adapter developers have control over location info property name. Tree adapters should implement setNodeSourceCodeLocation and getNodeSourceCodeLocation methods. Location info property name added by currently implemented tree adapters has been renamed from __location to sourceCodeLocation (GH #189).

• Updated (breaking): Location info line and col properties have been renamed to startLine and
  startCol
  respectively.

• Updated (breaking): SAXParser now passes token objects to event handlers instead of separate arguments. See SAXParser documentation for more info.
  (GH #247).

• Added: endLine and endCol location info
  properties.

• Added: scriptingEnabled flag to the ParserOptions which controls how <noscript> tags are handled by the parser. (GH #192).

• Added: HTML rewriting stream.
  (GH #222).

• Removed (breaking): parse5 no longer ship TypeScript definitions. Existing TypeScript definitions have been moved to DefinitelyTyped repo. Please, track the PR in the DefinitelyTyped repo for the updates.

v4.0.0

This is a major release that delivers few minor (but breaking) changes to workaround recently appeared issues with TypeScript Node.js typings versioning and usage of parse5 in environments that are distinct from Node.js (see #235 for the details).

• Updated (breaking): TypeScript were disabled by default. See TypeScript definitions section for the details on how to enable them.
• Updated: API that depends on Node.js specific (namely ParserStream, PlainTextConversionStream, SerializerStream, SAXParser) is now lazily loaded. That enables bundling of the basic functionality for other platforms (e.g. for browsers via webpack).

v3.0.3

• Fixed: Loosen the dependency version of @types/node (by @gfx).
• Fixed: Incorrect AST generated if empty string fed to ParserStream (GH #195) (by @stevenvachon).