- #175
4fcee24Thanks @LuLaValva! - Add support forsatisfies
- #171
aa98807Thanks @DylanPiercey! - Upgrade dependencies and configs
- #168
3a696d0Thanks @DylanPiercey! - When the preceding character of an expression is a quote, prefer division over regexp state. This improves parsing for inline css grid properties.
- #164
13a33a3Thanks @DylanPiercey! - Allow indented javascript style comments that are not under a parent tag in concise mode.
-
#161
be73442Thanks @DylanPiercey! - Fixes a regression where the parsed text state (used by egscript,style) was not properly entering back into text for the closing quote on the string. -
#162
085451cThanks @DylanPiercey! - Always consume next character of expression if terminator was preceded by an operator.
- #158
fe98530Thanks @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"
- #156
72b3379Thanks @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 asthing_andnew x.
-
#154
6b5b196Thanks @DylanPiercey! - In concise mode, a new line which starts with a coma will now continue attributes for the current tag. -
#154
6b5b196Thanks @DylanPiercey! - Allow a comma to follow the tag name to begin attributes.
- #154
61e6966Thanks @DylanPiercey! - Avoid continuing expressions after a period if after the whitespace is something that could not be an identifier.
- #152
ea65c9fThanks @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.
- #150
0d7210bThanks @DylanPiercey! - Fix issue with tag variable not terminated on concise mode text delimiter
- #148
948830eThanks @DylanPiercey! - Fix issue with semi-colon after a block scriptlet.
- #146
bcfd809Thanks @DylanPiercey! - Fixes an issue where attribute names that started with a keyword (eg:as-thingorinstanceof-thing) were incorrectly treated as an expression continuation.
- #143
635b97cThanks @DylanPiercey! - Fix issue where and extra character was being consumed if an escaped placeholder was at the end of a tag.
- #141
81cff30Thanks @DylanPiercey! - Add support for type parameter/argument parsing. This adds a newonTagTypeParams,onTagTypeArgsevents and a.typeParamsproperty on theAttrMethodrange.
- #138
8c34227Thanks @DylanPiercey! - Fixes a parse error where division is immediately followed by enclosed code.
- #136
b5fa4d0Thanks @DylanPiercey! - Optimize parser constructor to avoid initializing unecessary properties.
- #134
cdbc6b2Thanks @DylanPiercey! - Improve missing attribute error when the tag is immediately closed without the attribute value.
- #132
59a10d5Thanks @DylanPiercey! - Fix regression which caused script tags with a trailing comment as the same line as the closing tag to not always parse properly.
- #132
59a10d5Thanks @DylanPiercey! - Remove unecessary check for cdata inside parsed text state.
- #130
ebc850fThanks @DylanPiercey! - Switch from regexp based parsing for the expression continuations. This slightly improves performance and more importantly fixes usage of the parser in safari.
- #127
222b145Thanks @DylanPiercey! - Fix regression around JS style comments in the body by requiring that they are preceded by a whitespace.
- #125
725bcb3Thanks @DylanPiercey! - Expose some apis for generating position and location information.
- #123
b8bfcd9Thanks @DylanPiercey! - Comma will now always terminate a tag variable.
- #121
b1e68a3Thanks @DylanPiercey! - Fix regression that causes incorrect expression continuations after regexps.
- #119
28fde07Thanks @DylanPiercey! - Support JS line comments inside the open tag (previously just block comments could be used).
- #119
28fde07Thanks @DylanPiercey! - Support JS style comments in HTML bodies (previously allowed in parsed text and concise mode).
- #117
8bd3c40Thanks @DylanPiercey! - Fix issue with onCloseTagStart not called for text mode tags (eg style, script, textarea & html-comment).
- #114
14f3499Thanks @DylanPiercey! - RenameonTagNametoonOpenTagName. Add a newonOpenTagStartevent (beforeonOpenTagName). Split theonCloseTagevent into three new events:onClosetTagStart,onCloseTagName&onCloseTagEnd).
- #112
2ad4628Thanks @DylanPiercey! - Switch character position offsets for newlines to be to similar to vscode. Previously the newline was counted as the first character of the line, now it is the last character of the previous line.
- #110
281750aThanks @DylanPiercey! - Rename publish script to release in order to avoid a double publish in the CI
- #108
8a988f4Thanks @DylanPiercey! - Fix issue where parser would sometimes not consume enough characters and cause a bracket mismatch
- #103
a4e3635Thanks @DylanPiercey! - Fixes issue where expressions could consume an extra character when windows line endings used.
- #103
1f2c9b0Thanks @DylanPiercey! - When parsing unenclosed expressions we look backwards for unary operators preceded by a word break. This caused a false positive when a member expression was found with the operator name, eginput.new. Now we ensure that these operators are not in a member expression like this.
- #103
469b4bcThanks @DylanPiercey! - Improves consistency with v2 of the parser by allowing expressions to span multiple lines if the line is ended with the continuation. This change also allows html attributes and grouped concise attributes to span multiple lines with a new line before or after the continuation.
- #101
9034f55Thanks @DylanPiercey! - Parse tag variable type as an continuable expression.
- #99
b1a3008Thanks @DylanPiercey! - Fix expression continuations containing equals not consuming enough characters
- #95
c577179Thanks @DylanPiercey! - Switch from semantic-release to changesets