Skip to content

Releases: marko-js/htmljs-parser

v5.5.3

27 Nov 23:27
Compare
Choose a tag to compare

Patch Changes

v5.5.2

05 Jan 17:00
Compare
Choose a tag to compare

Patch Changes

v5.5.1

11 Nov 00:01
Compare
Choose a tag to compare

Patch Changes

  • #168 3a696d0 Thanks @DylanPiercey! - When the preceding character of an expression is a quote, prefer division over regexp state. This improves parsing for inline css grid properties.

v5.5.0

26 May 22:52
Compare
Choose a tag to compare

Minor Changes

  • #164 13a33a3 Thanks @DylanPiercey! - Allow indented javascript style comments that are not under a parent tag in concise mode.

v5.4.3

15 Mar 20:52
Compare
Choose a tag to compare

Patch Changes

  • #161 be73442 Thanks @DylanPiercey! - Fixes a regression where the parsed text state (used by eg script, style) was not properly entering back into text for the closing quote on the string.

  • #162 085451c Thanks @DylanPiercey! - Always consume next character of expression if terminator was preceded by an operator.

v5.4.2

13 Mar 22:56
Compare
Choose a tag to compare

Patch Changes

  • #158 fe98530 Thanks @DylanPiercey! - Fixes an regression where string literals inside of parsed text nodes (eg <script>) were not properly changing the parser state. This caused issues when comment like syntax was embedded within these string literals"

v5.4.1

11 Mar 22:14
Compare
Choose a tag to compare

Patch Changes

  • #156 72b3379 Thanks @DylanPiercey! - Fix regression where the parser would continue unary keyword expressions even if the keyword was inside a word boundary. Eg <div class=thing_new x> would cause the parser to see the expression as thing_ and new x.

v5.4.0

08 Mar 14:44
Compare
Choose a tag to compare

Minor Changes

Patch Changes

  • #154 61e6966 Thanks @DylanPiercey! - Avoid continuing expressions after a period if after the whitespace is something that could not be an identifier.

v5.3.0

27 Feb 15:08
33d280d
Compare
Choose a tag to compare

Minor Changes

  • #152 ea65c9f Thanks @DylanPiercey! - Improve handling ambiguity with tag type args vs type params. Type args must now always be directly adjacent the tag name, otherwise it will become type params.

v5.2.4

13 Feb 19:29
210427c
Compare
Choose a tag to compare

Patch Changes