This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@marko/language-server@3.4.1

Patch Changes

• #608 6d1f577 Thanks @DylanPiercey! - Require htmljs-parser 5.18.0, which ends a type at a trailing void, reads a TypeScript ! after an operand as a non-null assertion, reads delete as an operator, and reads types in scriptlets, so templates using them are no longer misparsed.

• #603 e4cd501 Thanks @DylanPiercey! - Keep formatting Marko files when the project's prettier config lists plugins, which replaced the Marko plugin so "Format Document" failed with Couldn't resolve parser "marko" and code-action fixes were left unformatted. The config's plugins are now resolved from the config file and loaded beside the Marko plugin, and one that cannot be loaded is skipped rather than failing the format.

• #601 2eb4dee Thanks @DylanPiercey! - Update prettier-plugin-marko to 4.1.1, so formatting a template whose code does not parse yet keeps the async on shorthand methods and the $ on scriptlets, and no longer lets a trailing line comment in an attribute value swallow the rest of the tag.

• #604 dec73df Thanks @DylanPiercey! - Update prettier-plugin-marko to 4.1.3, so formatting keeps the comments inside an open tag, which it deleted before, and no longer doubles the backslashes in text. A line comment that ends a tag var is moved into a block comment, since it would otherwise swallow the rest of the tag.

• Updated dependencies [6d1f577]:

  • @marko/language-tools@2.7.1

@marko/language-tools@2.7.1

Patch Changes

• #608 6d1f577 Thanks @DylanPiercey! - Require htmljs-parser 5.18.0, which ends a type at a trailing void, reads a TypeScript ! after an operand as a non-null assertion, reads delete as an operator, and reads types in scriptlets, so templates using them are no longer misparsed.

marko-vscode@3.2.1

Patch Changes

• #608 232857c Thanks @DylanPiercey! - Highlight attribute values the way the parser now reads them: a ! directly after an operand (x!, f()!, x!!, "s"!) is a non-null assertion that ends the value, void in a tag variable's type no longer runs on into the next attribute, and delete x stays one value.

• #603 e4cd501 Thanks @DylanPiercey! - Keep formatting Marko files when the project's prettier config lists plugins, which replaced the Marko plugin so "Format Document" failed with Couldn't resolve parser "marko" and code-action fixes were left unformatted. The config's plugins are now resolved from the config file and loaded beside the Marko plugin, and one that cannot be loaded is skipped rather than failing the format.

• #601 2eb4dee Thanks @DylanPiercey! - Update prettier-plugin-marko to 4.1.1, so formatting a template whose code does not parse yet keeps the async on shorthand methods and the $ on scriptlets, and no longer lets a trailing line comment in an attribute value swallow the rest of the tag.

• #604 dec73df Thanks @DylanPiercey! - Update prettier-plugin-marko to 4.1.3, so formatting keeps the comments inside an open tag, which it deleted before, and no longer doubles the backslashes in text. A line comment that ends a tag var is moved into a block comment, since it would otherwise swallow the rest of the tag.