htmljs-parser
Advanced tools
Changelog
5.5.1
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.Changelog
5.5.0
13a33a3
Thanks @DylanPiercey! - Allow indented javascript style comments that are not under a parent tag in concise mode.Changelog
5.4.3
#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.
Changelog
5.4.2
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"Changelog
5.4.1
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
.Changelog
5.4.0
#154 6b5b196
Thanks @DylanPiercey! - In concise mode, a new line which starts with a coma will now continue attributes for the current tag.
#154 6b5b196
Thanks @DylanPiercey! - Allow a comma to follow the tag name to begin attributes.
61e6966
Thanks @DylanPiercey! - Avoid continuing expressions after a period if after the whitespace is something that could not be an identifier.Changelog
5.3.0
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.Changelog
5.2.4
0d7210b
Thanks @DylanPiercey! - Fix issue with tag variable not terminated on concise mode text delimiter