build(deps-dev): bump the extension-dependencies group with 7 updates #339

dependabot · 2024-02-12T10:06:05Z

Bumps the extension-dependencies group with 7 updates:

Package	From	To
@types/node	`20.11.5`	`20.11.17`
@types/vscode	`1.85.0`	`1.86.0`
@typescript-eslint/eslint-plugin	`6.19.0`	`6.21.0`
@typescript-eslint/parser	`6.19.0`	`6.21.0`
@vscode/vsce	`2.22.0`	`2.23.0`
esbuild	`0.19.11`	`0.20.0`
prettier	`3.2.4`	`3.2.5`

Updates @types/node from 20.11.5 to 20.11.17

Commits

See full diff in compare view

Updates @types/vscode from 1.85.0 to 1.86.0

Commits

See full diff in compare view

Updates @typescript-eslint/eslint-plugin from 6.19.0 to 6.21.0

Release notes

Sourced from @typescript-eslint/eslint-plugin's releases.

v6.21.0

6.21.0 (2024-02-05)

🚀 Features

export plugin metadata (#8331)

allow parserOptions.project: false (#8339)

eslint-plugin: add rule prefer-find (#8216)

typescript-estree: forbid duplicated accessibility modifiers (#8257)

utils: improve eslint types (#8344)

🩹 Fixes

ast-spec: add JSXElement type to the JSXAttribute['value'] (#8285)

eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression (#8265)

eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values (#8250)

eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions (#8332)

eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option (#8249)

eslint-plugin: [class-literal-property-style] allow getter when same key setter exists (#8277)

eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword (#8326)

rule-tester: fix a phantom dependency on the "semver" package (#8260)

❤️ Thank You

auvred @auvred

Brad Zacher @bradzacher

Kirk Waiblinger @kirkwaiblinger

Pete Gonzalez @octogonz

YeonJuan @yeonjuan

You can read about our versioning strategy and releases on our website.

v6.20.0

6.20.0 (2024-01-29)

🚀 Features

eslint-plugin: [member-ordering] allow easy reuse of the default ordering (#8248)

🩹 Fixes

eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result (#8283)

eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable (#8262)

eslint-plugin: [no-useless-template-literals] report Infinity & NaN (#8295)

eslint-plugin: [prefer-readonly] disable checking accessors (#8300)

❤️ Thank You

... (truncated)

Changelog

Sourced from @typescript-eslint/eslint-plugin's changelog.

6.21.0 (2024-02-05)

🚀 Features

export plugin metadata

allow parserOptions.project: false

eslint-plugin: add rule prefer-find

🩹 Fixes

eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression

eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values

eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions

eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option

eslint-plugin: [class-literal-property-style] allow getter when same key setter exists

eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword

❤️ Thank You

auvred

Brad Zacher

Kirk Waiblinger

Pete Gonzalez

YeonJuan

You can read about our versioning strategy and releases on our website.

6.20.0 (2024-01-29)

🚀 Features

eslint-plugin: [member-ordering] allow easy reuse of the default ordering

🩹 Fixes

eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result

eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable

... (truncated)

Commits

289ee88 chore(release): publish 6.21.0
f892a72 docs(eslint-plugin): mention alternatives in no-explicit-any (#8370)
aa5edf7 chore(deps): update dependency prettier to v3.2.4 (#8357)
1d7447f chore(eslint-plugin): [no-invalid-void-type] fix Options typing to reflect ...
e2b46e0 fix(eslint-plugin): [no-unnecessary-type-assertion] provide valid fixes for a...
3bbb78d feat(eslint-plugin): add rule prefer-find (#8216)
9883ee2 feat: export plugin metadata (#8331)
69bd501 fix(eslint-plugin): [class-literal-property-style] allow getter when same key...
cd5dff8 chore: bump eslint versions (#8338)
8d62ee6 chore: remove unnecessary eslint-disable comments (#8336)
Additional commits viewable in compare view

Updates @typescript-eslint/parser from 6.19.0 to 6.21.0

Release notes

Sourced from @typescript-eslint/parser's releases.

v6.21.0

6.21.0 (2024-02-05)

🚀 Features

export plugin metadata (#8331)

allow parserOptions.project: false (#8339)

eslint-plugin: add rule prefer-find (#8216)

typescript-estree: forbid duplicated accessibility modifiers (#8257)

utils: improve eslint types (#8344)

🩹 Fixes

ast-spec: add JSXElement type to the JSXAttribute['value'] (#8285)

eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression (#8265)

eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values (#8250)

eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions (#8332)

eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option (#8249)

eslint-plugin: [class-literal-property-style] allow getter when same key setter exists (#8277)

eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before as keyword (#8326)

rule-tester: fix a phantom dependency on the "semver" package (#8260)

❤️ Thank You

auvred @auvred

Brad Zacher @bradzacher

Kirk Waiblinger @kirkwaiblinger

Pete Gonzalez @octogonz

YeonJuan @yeonjuan

You can read about our versioning strategy and releases on our website.

v6.20.0

6.20.0 (2024-01-29)

🚀 Features

eslint-plugin: [member-ordering] allow easy reuse of the default ordering (#8248)

🩹 Fixes

eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result (#8283)

eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable (#8262)

eslint-plugin: [no-useless-template-literals] report Infinity & NaN (#8295)

eslint-plugin: [prefer-readonly] disable checking accessors (#8300)

❤️ Thank You

... (truncated)

Changelog

Sourced from @typescript-eslint/parser's changelog.

6.21.0 (2024-02-05)

🚀 Features

allow parserOptions.project: false

❤️ Thank You

auvred

Brad Zacher

Kirk Waiblinger

Pete Gonzalez

YeonJuan

You can read about our versioning strategy and releases on our website.

6.20.0 (2024-01-29)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

6.19.1 (2024-01-22)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits

289ee88 chore(release): publish 6.21.0
aa5edf7 chore(deps): update dependency prettier to v3.2.4 (#8357)
45c0cb2 chore: cleanup test-utils naming/locations (#8341)
a01a6e6 chore(release): publish 6.20.0
a911214 chore(release): publish 6.19.1
See full diff in compare view

Updates @vscode/vsce from 2.22.0 to 2.23.0

Commits

6e959ca remove fixture files (#925)
f37621d fixes #322 (#924)
3fc1a9a publish pre-release on main ci (#923)
1be75b2 feat: show targets in show command (#922)
4df2693 show pre-release data in show command (#921)
b18c620 rewrite video src links (#920)
916fd91 feat: support --readme-path and --changelog-path (#919)
302f02c handle multi line images (#918)
160d0e0 Filter data from other platforms (#912)
3e8410b feat: Support for yarn workspaces (#493)
Additional commits viewable in compare view

Updates esbuild from 0.19.11 to 0.20.0

Release notes

Sourced from esbuild's releases.

v0.20.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

Work around API deprecations in Deno 1.40.x (#3609, #3611)

Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

Reorder implicit file extensions within node_modules (#3341, #3608)

In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

v0.19.12
The "preserve" JSX mode now preserves JSX text verbatim (#3605)

The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
// Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'&quot;}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
{foo}
more text </a>;
Allow JSX elements as JSX attribute values

JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.20.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

Work around API deprecations in Deno 1.40.x (#3609, #3611)

Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

Reorder implicit file extensions within node_modules (#3341, #3608)

In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

0.19.12
The "preserve" JSX mode now preserves JSX text verbatim (#3605)

The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
// Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'&quot;}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
{foo}
more text </a>;
Allow JSX elements as JSX attribute values

... (truncated)

Commits

2af5ccf publish 0.20.0 to npm
0bccf08 fix esbuild/deno-esbuild#5
931f87d work around api deprecations in deno 1.40.x (#3609) (#3611)
22a9cf5 fix #3341, fix #3608: sort .ts right after .js
f8ec300 run npm pkg fix as suggested by the npm cli
d7fd1ad publish 0.19.12 to npm
e04a690 fix #3605: print the original JSX AST unmodified
f571399 allow jsx elements as jsx attribute values
a652e73 run make update-compat-table
35c0d65 fix #3574: ts type parser bug with infer + extends
Additional commits viewable in compare view

Updates prettier from 3.2.4 to 3.2.5

Release notes

Sourced from prettier's releases.

3.2.5

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.2.5

diff

Support Angular inline styles as single template literal (#15968 by `@sosukesuzuki`)

Angular v17 supports single string inline styles.

// Input
@Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}
// Prettier 3.2.4
@Component({
template: &lt;div&gt;...&lt;/div&gt;,
styles: h1 { color: blue; },
})
export class AppComponent {}
// Prettier 3.2.5
@Component({
template: &lt;div&gt;...&lt;/div&gt;,
styles: h1 { color: blue; },
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#15969 by `@JounQin`)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";
@Component({
[template]: &lt;h1&gt;{{       hello }}&lt;/h1&gt;,
})
export class AppComponent {}
</tr></table>

... (truncated)

Commits

7142cf3 Release 3.2.5
8cbee2e chore(deps): update glimmer to v0.88.1 (#15991)
45baee0 chore(deps): update dependency magic-string to v0.30.6 (#16022)
9fb32a1 Minor refactor to property print (#15924)
08f1940 Update install script for husky v9 (#16000)
6d0b1d2 Update yarn to v4.1.0 (#16021)
c8ba8db chore(deps): update dependency @angular/compiler to v17.1.2 (#16018)
e2250ec chore(deps): update typescript-eslint to v6.20.0 (#16015)
02865f6 chore(deps): update dependency npm-run-all2 to v6.1.2 (#16017)
014ee5d chore(deps): update dependency hermes-parser to v0.19.0 (#16014)
Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
@types/node	[>= 18.a, < 19]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the extension-dependencies group with 7 updates: | Package | From | To | | --- | --- | --- | | [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `20.11.5` | `20.11.17` | | [@types/vscode](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/vscode) | `1.85.0` | `1.86.0` | | [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) | `6.19.0` | `6.21.0` | | [@typescript-eslint/parser](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/parser) | `6.19.0` | `6.21.0` | | [@vscode/vsce](https://github.com/Microsoft/vsce) | `2.22.0` | `2.23.0` | | [esbuild](https://github.com/evanw/esbuild) | `0.19.11` | `0.20.0` | | [prettier](https://github.com/prettier/prettier) | `3.2.4` | `3.2.5` | Updates `@types/node` from 20.11.5 to 20.11.17 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) Updates `@types/vscode` from 1.85.0 to 1.86.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/vscode) Updates `@typescript-eslint/eslint-plugin` from 6.19.0 to 6.21.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.21.0/packages/eslint-plugin) Updates `@typescript-eslint/parser` from 6.19.0 to 6.21.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/parser/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v6.21.0/packages/parser) Updates `@vscode/vsce` from 2.22.0 to 2.23.0 - [Release notes](https://github.com/Microsoft/vsce/releases) - [Commits](microsoft/vscode-vsce@v2.22.0...v2.23.0) Updates `esbuild` from 0.19.11 to 0.20.0 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.19.11...v0.20.0) Updates `prettier` from 3.2.4 to 3.2.5 - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](prettier/prettier@3.2.4...3.2.5) --- updated-dependencies: - dependency-name: "@types/node" dependency-type: direct:development update-type: version-update:semver-patch dependency-group: extension-dependencies - dependency-name: "@types/vscode" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: extension-dependencies - dependency-name: "@typescript-eslint/eslint-plugin" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: extension-dependencies - dependency-name: "@typescript-eslint/parser" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: extension-dependencies - dependency-name: "@vscode/vsce" dependency-type: direct:development update-type: version-update:semver-minor dependency-group: extension-dependencies - dependency-name: esbuild dependency-type: direct:development update-type: version-update:semver-minor dependency-group: extension-dependencies - dependency-name: prettier dependency-type: direct:development update-type: version-update:semver-patch dependency-group: extension-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2024-02-19T09:45:45Z

Superseded by #340.

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Feb 12, 2024

dependabot bot mentioned this pull request Feb 12, 2024

build(deps-dev): bump the extension-dependencies group with 7 updates #338

Closed

dependabot bot closed this Feb 19, 2024

dependabot bot deleted the dependabot/npm_and_yarn/extension-dependencies-7f05e2b305 branch February 19, 2024 09:45

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

build(deps-dev): bump the extension-dependencies group with 7 updates #339

build(deps-dev): bump the extension-dependencies group with 7 updates #339

dependabot bot commented on behalf of github Feb 12, 2024 •

edited

Loading

dependabot bot commented on behalf of github Feb 19, 2024

build(deps-dev): bump the extension-dependencies group with 7 updates #339

build(deps-dev): bump the extension-dependencies group with 7 updates #339

Conversation

dependabot bot commented on behalf of github Feb 12, 2024 • edited Loading

v6.21.0

6.21.0 (2024-02-05)

🚀 Features

🩹 Fixes

❤️ Thank You

v6.20.0

6.20.0 (2024-01-29)

🚀 Features

🩹 Fixes

❤️ Thank You

6.21.0 (2024-02-05)

🚀 Features

🩹 Fixes

❤️ Thank You

6.20.0 (2024-01-29)

🚀 Features

🩹 Fixes

v6.21.0

6.21.0 (2024-02-05)

🚀 Features

🩹 Fixes

❤️ Thank You

v6.20.0

6.20.0 (2024-01-29)

🚀 Features

🩹 Fixes

❤️ Thank You

6.21.0 (2024-02-05)

🚀 Features

❤️ Thank You

6.20.0 (2024-01-29)

6.19.1 (2024-01-22)

v0.20.0

v0.19.12

0.20.0

0.19.12

3.2.5

3.2.5

Support Angular inline styles as single template literal (#15968 by @​sosukesuzuki)

Unexpected embedded formatting for Angular template (#15969 by @​JounQin)

dependabot bot commented on behalf of github Feb 19, 2024

dependabot bot commented on behalf of github Feb 12, 2024 •

edited

Loading

Support Angular inline styles as single template literal (#15968 by `@sosukesuzuki`)

Unexpected embedded formatting for Angular template (#15969 by `@JounQin`)