favware / esbuild-plugin-file-path-extensions

An esbuild plugin to automatically insert file extensions in your built JavaScript files based on the specified target
MIT License
21 stars 2 forks source link

chore(deps): update all non-major dependencies #39

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@commitlint/cli (source) ^17.7.1 -> ^17.7.2 age adoption passing confidence
@types/node (source) ^18.17.19 -> ^18.18.1 age adoption passing confidence
@typescript-eslint/eslint-plugin ^6.7.2 -> ^6.7.3 age adoption passing confidence
@typescript-eslint/parser ^6.7.2 -> ^6.7.3 age adoption passing confidence
esbuild ^0.19.3 -> ^0.19.4 age adoption passing confidence
vitest ^0.34.5 -> ^0.34.6 age adoption passing confidence

Release Notes

conventional-changelog/commitlint (@​commitlint/cli) ### [`v17.7.2`](https://togithub.com/conventional-changelog/commitlint/blob/HEAD/@​commitlint/cli/CHANGELOG.md#1772-2023-09-28) [Compare Source](https://togithub.com/conventional-changelog/commitlint/compare/v17.7.1...v17.7.2) **Note:** Version bump only for package [@​commitlint/cli](https://togithub.com/commitlint/cli)
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin) ### [`v6.7.3`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#673-2023-09-25) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.2...v6.7.3) **Note:** Version bump only for package [@​typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
typescript-eslint/typescript-eslint (@​typescript-eslint/parser) ### [`v6.7.3`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#673-2023-09-25) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v6.7.2...v6.7.3) **Note:** Version bump only for package [@​typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
evanw/esbuild (esbuild) ### [`v0.19.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0194) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.3...v0.19.4) - Fix printing of JavaScript decorators in tricky cases ([#​3396](https://togithub.com/evanw/esbuild/issues/3396)) This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples: ```js // Original code import { constant } from './constants.js' import { imported } from 'external' import { undef } from './empty.js' class Foo { @​constant() @​imported() @​undef() foo } // Old output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @​123() @​(0, import_external.imported)() @​(void 0)() foo; }; // New output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @​(123()) @​((0, import_external.imported)()) @​((void 0)()) foo; }; ``` - Allow pre-release versions to be passed to `target` ([#​3388](https://togithub.com/evanw/esbuild/issues/3388)) People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's `target` setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to `target` and do something reasonable with them.
vitest-dev/vitest (vitest) ### [`v0.34.6`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.6) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.34.5...v0.34.6) #####    🐞 Bug Fixes - Overwrite global URL with environment's  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/4164](https://togithub.com/vitest-dev/vitest/issues/4164) [(cbe13)](https://togithub.com/vitest-dev/vitest/commit/cbe133da) - Correctly resolve external dependencies loaded by custom environments  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/4196](https://togithub.com/vitest-dev/vitest/issues/4196) [(e3408)](https://togithub.com/vitest-dev/vitest/commit/e340802f) - **runner**: The fixture of `test.extend` should be init once time in all test  -  by [@​Dunqing](https://togithub.com/Dunqing) in [https://github.com/vitest-dev/vitest/issues/4168](https://togithub.com/vitest-dev/vitest/issues/4168) [(730b2)](https://togithub.com/vitest-dev/vitest/commit/730b29ec) #####     [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.34.5...v0.34.6)

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.



This PR has been generated by Mend Renovate. View repository job log here.