esbuild-plugin-browserslist icon indicating copy to clipboard operation
esbuild-plugin-browserslist copied to clipboard

Published 20 hours ago • verified publisher icon nihalgonsalves

chore(deps): bump the all group across 1 directory with 9 updates

Open dependabot[bot] opened this issue 1 year ago • 0 comments

Bumps the all group with 9 updates in the / directory:

Package From To
zod 3.23.5 3.23.8
@nihalgonsalves/esconfig 0.9.9 0.9.10
@types/node 18.19.31 18.19.33
@vitest/coverage-v8 1.5.2 1.6.0
@vitest/ui 1.5.2 1.6.0
esbuild 0.20.2 0.21.3
eslint-plugin-vitest 0.4.1 0.5.4
lefthook 1.6.10 1.6.12
vitest 1.5.2 1.6.0

Updates zod from 3.23.5 to 3.23.8

Release notes

Sourced from zod's releases.

v3.23.8

Commits:

  • 0f4d403558ae0490c711e4c2bfcf6c200bd14e11 Add Bronze logos (#3470)
  • 19687315b5b24bbd1ff6c346bfc2975700221748 Tweak tiers (#3471)
  • eda7df314399929f7ed737423868a5a0780cd944 Change RefinementCtx to interface
  • ca42965df46b2f7e2747db29c40a26bcb32a51d5 v3.23.8

v3.23.7

Commits:

  • 29d2ea2a15f0b1ac4b89138041f786a3dafc490b Add copper
  • d969423266fccee56ef769da6744cc8bacb04550 Fix #3437: extendShape erases JSDoc property documentation (#3463)
  • 2239ff3ccc9af4d28bee27bd6fb2a5632844480b Add social crow
  • f985b5b922cb357dbf4b25bb43814d19f838e046 3.23.7

v3.23.6

Commits:

  • bc0095aab9e7254deb18701adc63de128ca2c742 Test on latest node
  • 6e5699a30373cc22879f2bcb6902fc138518c980 Lint on latest node
  • 1f466d9d00f446d7bed1962990e7a1ce813ab0d4 describe how one can protect from cyclical objects starting an infini… (#3447)
  • 3fed6f21e0ea7adc91aa0cc44f75bcf4e526d98e Add zod playground link (#3454)
  • 04e1f379f6989d23dd45660fcabc78f76d7834f8 Fixed freezing async ZodReadonly results (#3457)
  • b87e59d0e4bbb4403bf27243afdcda9fcdeec258 Update sponsor tiers (#3453)
  • 143886151bba3930bdcc10d34a1cff4bf9103ba8 Add copper tier (#3460)
  • ce3711e1384952d255769b9495f9bfadfb327291 add VSCode dev container support and documenation
  • 93b480b12ec3466cbd3b4182f7ce292e5c61528c v3.23.6
Commits

Updates @nihalgonsalves/esconfig from 0.9.9 to 0.9.10

Release notes

Sourced from @​nihalgonsalves/esconfig's releases.

esconfig: v0.9.10

0.9.10 (2024-05-06)

Features

  • deps: bump the all group with 2 updates (#101) (29cfc21)
Changelog

Sourced from @​nihalgonsalves/esconfig's changelog.

0.9.10 (2024-05-06)

Features

  • deps: bump the all group with 2 updates (#101) (29cfc21)
Commits

Updates @types/node from 18.19.31 to 18.19.33

Commits

Updates @vitest/coverage-v8 from 1.5.2 to 1.6.0

Release notes

Sourced from @​vitest/coverage-v8's releases.

v1.6.0

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

    View changes on GitHub
Commits

Updates @vitest/ui from 1.5.2 to 1.6.0

Release notes

Sourced from @​vitest/ui's releases.

v1.6.0

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

    View changes on GitHub
Commits

Updates esbuild from 0.20.2 to 0.21.3

Release notes

Sourced from esbuild's releases.

v0.21.3

  • Implement the decorator metadata proposal (#3760)

    This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

    // Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

    const track = (_, context) => {
(context.metadata.names ||= []).push(context.name)
}
    

    class Foo {
@​track foo = 1
@​track bar = 2
}
    

    // Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)

    ⚠️ WARNING ⚠️

    This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Fix bundled decorators in derived classes (#3768)

    In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

    class Foo extends Object {
  @(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())

  • Fix tsconfig.json files inside symlinked directories (#3767)

    This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

v0.21.2

  • Correct this in field and accessor decorators (#3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

    const dec = () => function() { this.bar = true }

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.3

  • Implement the decorator metadata proposal (#3760)

    This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

    // Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

    const track = (_, context) => {
(context.metadata.names ||= []).push(context.name)
}
    

    class Foo {
@​track foo = 1
@​track bar = 2
}
    

    // Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)

    ⚠️ WARNING ⚠️

    This proposal has been marked as "stage 3" which means "recommended for implementation". However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Fix bundled decorators in derived classes (#3768)

    In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

    class Foo extends Object {
  @(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())

  • Fix tsconfig.json files inside symlinked directories (#3767)

    This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

0.21.2

  • Correct this in field and accessor decorators (#3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

... (truncated)

Commits
  • efa3dd2 publish 0.21.3 to npm
  • 5e7cf25 fix #3760: implement decorator metadata proposal
  • bd0b13b lowering: always propagate class expression names
  • 90acd14 explicit bitwise operators for initializer flags
  • ba548df move decorator initializer list to after the class
  • 66b7c6d fix #3768: bundled decorators in derived classes
  • 6e6f15f fix #3767: tsconfig.json files inside symlinks
  • b7dcb95 transform: reuse lowerField for auto-accessors
  • b24180e publish 0.21.2 to npm
  • f82e0ad fix #3761: this in field and accessor decorators
  • Additional commits viewable in compare view

Updates eslint-plugin-vitest from 0.4.1 to 0.5.4

Release notes

Sourced from eslint-plugin-vitest's releases.

v0.5.4

Features

  • support old Eslint configuration
  • update dependencies

v0.5.3

Bug Fixes

v0.5.2

Features

v0.5.1

Bug Fixes

  • no-focused-tests: support .each template strings (#420) (36e5b9a)

v0.5.0

‼️ Breaking Change 🚨

This version only supports new eslint flat config!

If you run into issues, consider downgrading and opening an issue. Remember to include a minimum repro example to help me fix issues quickly!

Full Changelog: https://github.com/veritem/eslint-plugin-vitest/compare/v0.5.0...v0.5.0

v0.4.2-beta.5

No release notes provided.

v0.4.2-beta.4

Bug Fixes

v0.4.2-beta.3

Features

... (truncated)

Commits

Updates lefthook from 1.6.10 to 1.6.12

Release notes

Sourced from lefthook's releases.

v1.6.12

Changelog

  • e87cc77 1.6.12: fix interactive mode for scripts
  • e42043f fix: enable interactive scripts (#720)
  • ce8d4f2 fix: more verbose error on versions mismatch (#721)

v1.6.11

Changelog

  • fd407ef 1.6.11: fix partially staged logic and add --no-auto-install flag
  • 1d100c6 chore: bump go to 1.22 (#701)
  • 6965783 feat: add run --no-auto-install flag (#716)
  • 5c6d8ae fix: add --porcelain to git status --short (#711)
Changelog

Sourced from lefthook's changelog.

1.6.12 (2024-05-17)

1.6.11 (2024-05-13)

Commits
  • e87cc77 1.6.12: fix interactive mode for scripts
  • ce8d4f2 fix: more verbose error on versions mismatch (#721)
  • e42043f fix: enable interactive scripts (#720)
  • fd407ef 1.6.11: fix partially staged logic and add --no-auto-install flag
  • 6965783 feat: add run --no-auto-install flag (#716)
  • 5c6d8ae fix: add --porcelain to git status --short (#711)
  • 1d100c6 chore: bump go to 1.22 (#701)
  • See full diff in compare view

Updates vitest from 1.5.2 to 1.6.0

Release notes

Sourced from vitest's releases.

v1.6.0

   🚀 Features

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

    View changes on GitHub
Commits
  • 6b29f3d chore: release v1.6.0
  • f8d3d22 feat(benchmark): support comparing benchmark result (#5398)
  • 21e58bd feat(browser): allow injecting scripts (#5656)
  • 30f728b feat: custom "snapshotEnvironment" option (#5449)
  • 2f91322 feat(reporter): support includeConsoleOutput and addFileAttribute in juni...
  • c571276 perf: unnecessary rpc call when coverage is disabled (#5658)
  • bdce0a2 feat: support standalone mode (#5565)
  • 40c299f fix: don't panic on empty files in node_modules
  • c9e68ce fix: hash the name of the file when caching (#5654)
  • f5faf42 fix: call resolveId('vitest') after buildStart (#5646)
  • Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
@types/node [>= 20.a, < 21]

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

dependabot[bot] avatar May 20 '24 19:05 dependabot[bot]