search

dominikg / tsconfck

A utility to find and parse tsconfig files without depending on typescript
Other
293 stars 14 forks source link

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

Closed renovate[bot] closed 2 years ago

renovate[bot] commented 2 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@commitlint/cli (source) ^16.0.2 -> ^16.1.0 age adoption passing confidence
@types/node ^16.11.19 -> ^16.11.21 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.9.1 -> ^5.10.0 age adoption passing confidence
@typescript-eslint/parser ^5.9.1 -> ^5.10.0 age adoption passing confidence
esbuild ^0.14.11 -> ^0.14.13 age adoption passing confidence
lint-staged ^12.1.7 -> ^12.3.1 age adoption passing confidence
typescript (source) ^4.5.4 -> ^4.5.5 age adoption passing confidence

Release Notes

conventional-changelog/commitlint ### [`v16.1.0`](https://togithub.com/conventional-changelog/commitlint/blob/HEAD/@​commitlint/cli/CHANGELOG.md#​1610-httpsgithubcomconventional-changelogcommitlintcomparev1603v1610-2022-01-20) [Compare Source](https://togithub.com/conventional-changelog/commitlint/compare/v16.0.3...v16.1.0) **Note:** Version bump only for package [@​commitlint/cli](https://togithub.com/commitlint/cli) #### [16.0.3](https://togithub.com/conventional-changelog/commitlint/compare/v16.0.2...v16.0.3) (2022-01-19) **Note:** Version bump only for package [@​commitlint/cli](https://togithub.com/commitlint/cli) #### [16.0.2](https://togithub.com/conventional-changelog/commitlint/compare/v16.0.1...v16.0.2) (2022-01-09) **Note:** Version bump only for package [@​commitlint/cli](https://togithub.com/commitlint/cli) #### [16.0.1](https://togithub.com/conventional-changelog/commitlint/compare/v16.0.0...v16.0.1) (2021-12-28) **Note:** Version bump only for package [@​commitlint/cli](https://togithub.com/commitlint/cli) ### [`v16.0.3`](https://togithub.com/conventional-changelog/commitlint/blob/HEAD/@​commitlint/cli/CHANGELOG.md#​1603-httpsgithubcomconventional-changelogcommitlintcomparev1602v1603-2022-01-19) [Compare Source](https://togithub.com/conventional-changelog/commitlint/compare/v16.0.2...v16.0.3) **Note:** Version bump only for package [@​commitlint/cli](https://togithub.com/commitlint/cli)
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin) ### [`v5.10.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#​5100-httpsgithubcomtypescript-eslinttypescript-eslintcomparev591v5100-2022-01-17) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.9.1...v5.10.0) ##### Bug Fixes - **eslint-plugin:** \[explicit-function-return-type] support AllowTypedFunctionExpression within AllowHigherOrderFunction ([#​4250](https://togithub.com/typescript-eslint/typescript-eslint/issues/4250)) ([d053cde](https://togithub.com/typescript-eslint/typescript-eslint/commit/d053cde3e8b5bf9ba1c22fd64a7456d672ef77ca)) - **eslint-plugin:** \[no-extra-semi] false negatives when used with eslint 8.3.0 ([#​4458](https://togithub.com/typescript-eslint/typescript-eslint/issues/4458)) ([f4016c2](https://togithub.com/typescript-eslint/typescript-eslint/commit/f4016c24f9023e8a42def9501b68c4a908cbfede)) - **eslint-plugin:** \[no-invalid-this] crash when used with eslint 8.7.0 ([#​4448](https://togithub.com/typescript-eslint/typescript-eslint/issues/4448)) ([e56f1e5](https://togithub.com/typescript-eslint/typescript-eslint/commit/e56f1e5d52fcbf3caae43034872e0b3181871689)) - **eslint-plugin:** \[no-magic-numbers] handle bigint in class props ([#​4411](https://togithub.com/typescript-eslint/typescript-eslint/issues/4411)) ([c8e650f](https://togithub.com/typescript-eslint/typescript-eslint/commit/c8e650f0c124d24b24beaeb376eaf61ee8d9e6fb)) ##### Features - rename `experimental-utils` to `utils` and make `experimental-utils` an alias to the new package ([#​4172](https://togithub.com/typescript-eslint/typescript-eslint/issues/4172)) ([1d55a75](https://togithub.com/typescript-eslint/typescript-eslint/commit/1d55a7511b38d8e2b2eabe59f639e0a865e6c93f)) #### [5.9.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.9.0...v5.9.1) (2022-01-10) **Note:** Version bump only for package [@​typescript-eslint/eslint-plugin](https://togithub.com/typescript-eslint/eslint-plugin)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser) ### [`v5.10.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#​5100-httpsgithubcomtypescript-eslinttypescript-eslintcomparev591v5100-2022-01-17) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.9.1...v5.10.0) ##### Features - rename `experimental-utils` to `utils` and make `experimental-utils` an alias to the new package ([#​4172](https://togithub.com/typescript-eslint/typescript-eslint/issues/4172)) ([1d55a75](https://togithub.com/typescript-eslint/typescript-eslint/commit/1d55a7511b38d8e2b2eabe59f639e0a865e6c93f)) #### [5.9.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.9.0...v5.9.1) (2022-01-10) **Note:** Version bump only for package [@​typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
evanw/esbuild ### [`v0.14.13`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01413) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.12...v0.14.13) - Be more consistent about external paths ([#​619](https://togithub.com/evanw/esbuild/issues/619)) The rules for marking paths as external using `--external:` grew over time as more special-cases were added. This release reworks the internal representation to be more straightforward and robust. A side effect is that wildcard patterns can now match post-resolve paths in addition to pre-resolve paths. Specifically you can now do `--external:./node_modules/*` to mark all files in the `./node_modules/` directory as external. This is the updated logic: - Before path resolution begins, import paths are checked against everything passed via an `--external:` flag. In addition, if something looks like a package path (i.e. doesn't start with `/` or `./` or `../`), import paths are checked to see if they have that package path as a path prefix (so `--external:@​foo/bar` matches the import path `@foo/bar/baz`). - After path resolution ends, the absolute paths are checked against everything passed via `--external:` that doesn't look like a package path (i.e. that starts with `/` or `./` or `../`). But before checking, the pattern is transformed to be relative to the current working directory. - Attempt to explain why esbuild can't run ([#​1819](https://togithub.com/evanw/esbuild/issues/1819)) People sometimes try to install esbuild on one OS and then copy the `node_modules` directory over to another OS without reinstalling. This works with JavaScript code but doesn't work with esbuild because esbuild is a native binary executable. This release attempts to offer a helpful error message when this happens. It looks like this: $ ./node_modules/.bin/esbuild ./node_modules/esbuild/bin/esbuild:106 throw new Error(` ^ Error: You installed esbuild on another platform than the one you're currently using. This won't work because esbuild is written with native code and needs to install a platform-specific binary executable. Specifically the "esbuild-linux-arm64" package is present but this platform needs the "esbuild-darwin-arm64" package instead. People often get into this situation by installing esbuild on Windows or macOS and copying "node_modules" into a Docker image that runs Linux, or by copying "node_modules" between Windows and WSL environments. If you are installing with npm, you can try not copying the "node_modules" directory when you copy the files over, and running "npm ci" or "npm install" on the destination platform after the copy. Or you could consider using yarn instead which has built-in support for installing a package on multiple platforms simultaneously. If you are installing with yarn, you can try listing both this platform and the other platform in your ".yarnrc.yml" file using the "supportedArchitectures" feature: https://yarnpkg.com/configuration/yarnrc/#supportedArchitectures Keep in mind that this means multiple copies of esbuild will be present. Another alternative is to use the "esbuild-wasm" package instead, which works the same way on all platforms. But it comes with a heavy performance cost and can sometimes be 10x slower than the "esbuild" package, so you may also not want to do that. at generateBinPath (./node_modules/esbuild/bin/esbuild:106:17) at Object. (./node_modules/esbuild/bin/esbuild:161:39) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:17:47 ### [`v0.14.12`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01412) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.14.11...v0.14.12) - Ignore invalid `@import` rules in CSS ([#​1946](https://togithub.com/evanw/esbuild/issues/1946)) In CSS, `@import` rules must come first before any other kind of rule (except for `@charset` rules). Previously esbuild would warn about incorrectly ordered `@import` rules and then hoist them to the top of the file. This broke people who wrote invalid `@import` rules in the middle of their files and then relied on them being ignored. With this release, esbuild will now ignore invalid `@import` rules and pass them through unmodified. This more accurately follows the CSS specification. Note that this behavior differs from other tools like Parcel, which does hoist CSS `@import` rules. - Print invalid CSS differently ([#​1947](https://togithub.com/evanw/esbuild/issues/1947)) This changes how esbuild prints nested `@import` statements that are missing a trailing `;`, which is invalid CSS. The result is still partially invalid CSS, but now printed in a better-looking way: ```css /* Original code */ .bad { @​import url("other") } .red { background: red; } /* Old output (with --minify) */ .bad{@​import url(other) } .red{background: red;}} /* New output (with --minify) */ .bad{@​import url(other);}.red{background:red} ``` - Warn about CSS nesting syntax ([#​1945](https://togithub.com/evanw/esbuild/issues/1945)) There's a proposed [CSS syntax for nesting rules](https://drafts.csswg.org/css-nesting/) using the `&` selector, but it's not currently implemented in any browser. Previously esbuild silently passed the syntax through untransformed. With this release, esbuild will now warn when you use nesting syntax with a `--target=` setting that includes a browser. - Warn about `}` and `>` inside JSX elements The `}` and `>` characters are invalid inside JSX elements according to [the JSX specification](https://facebook.github.io/jsx/) because they commonly result from typos like these that are hard to catch in code reviews: ```jsx function F() { return
>
; } function G() { return
{1}}
; } ``` The TypeScript compiler already [treats this as an error](https://togithub.com/microsoft/TypeScript/issues/36341), so esbuild now treats this as an error in TypeScript files too. That looks like this: ✘ [ERROR] The character ">" is not valid inside a JSX element example.tsx:2:14: 2 │ return
>
; │ ^ ╵ {'>'} Did you mean to escape it as "{'>'}" instead? ✘ [ERROR] The character "}" is not valid inside a JSX element example.tsx:5:17: 5 │ return
{1}}
; │ ^ ╵ {'}'} Did you mean to escape it as "{'}'}" instead? Babel doesn't yet treat this as an error, so esbuild only warns about these characters in JavaScript files for now. Babel 8 [treats this as an error](https://togithub.com/babel/babel/issues/11042) but Babel 8 [hasn't been released yet](https://togithub.com/babel/babel/issues/10746). If you see this warning, I recommend fixing the invalid JSX syntax because it will become an error in the future. - Warn about basic CSS property typos This release now generates a warning if you use a CSS property that is one character off from a known CSS property: ▲ [WARNING] "marign-left" is not a known CSS property example.css:2:2: 2 │ marign-left: 12px; │ ~~~~~~~~~~~ ╵ margin-left Did you mean "margin-left" instead?
okonet/lint-staged ### [`v12.3.1`](https://togithub.com/okonet/lint-staged/releases/v12.3.1) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v12.3.0...v12.3.1) ##### Bug Fixes - **deps:** update dependencies ([f190fc3](https://togithub.com/okonet/lint-staged/commit/f190fc31888d0a3c6f7070cb0f97edcbc7018a0e)) ### [`v12.3.0`](https://togithub.com/okonet/lint-staged/releases/v12.3.0) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v12.2.2...v12.3.0) ##### Features - add `--cwd` option for overriding task directory ([62b5b83](https://togithub.com/okonet/lint-staged/commit/62b5b833950774e731b0ca034aa9289ec254a602)) ### [`v12.2.2`](https://togithub.com/okonet/lint-staged/releases/v12.2.2) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v12.2.1...v12.2.2) ##### Bug Fixes - always search config from `cwd` first ([4afcda5](https://togithub.com/okonet/lint-staged/commit/4afcda5addade65ef847e3c5b0c4a38db80d020b)) ### [`v12.2.1`](https://togithub.com/okonet/lint-staged/releases/v12.2.1) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v12.2.0...v12.2.1) ##### Bug Fixes - only throw if no configurations were found ([36b9546](https://togithub.com/okonet/lint-staged/commit/36b9546dda5ca24174b519ce6d132f31077b093b)) ### [`v12.2.0`](https://togithub.com/okonet/lint-staged/releases/v12.2.0) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v12.1.7...v12.2.0) ##### Bug Fixes - make console task titles more explicit ([1c94c27](https://togithub.com/okonet/lint-staged/commit/1c94c2780485f3a2273f8b82db8e74ecafe258b4)) ##### Features - support multiple configuration files ([90d1035](https://togithub.com/okonet/lint-staged/commit/90d1035ef709329d297272e9164b0452c1ed37bd))
Microsoft/TypeScript ### [`v4.5.5`](https://togithub.com/Microsoft/TypeScript/releases/v4.5.5) [Compare Source](https://togithub.com/Microsoft/TypeScript/compare/v4.5.4...v4.5.5) This [patch release](https://togithub.com/microsoft/TypeScript/issues?q=is%3Aissue+milestone%3A%22TypeScript+4.5.5%22+is%3Aclosed) includes a number of fixes to language service crashes and assertion violations, along with improvements to JSX attribute snippets. For the complete list of fixed issues, check out the - [fixed issues query for Typescript 4.5.0 (Beta)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.5.0%22+). - [fixed issues query for Typescript 4.5.1 (RC)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.5.1%22+). - [fixed issues query for Typescript 4.5.2 (Stable)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.5.2%22+). - [fixed issues query for Typescript 4.5.3 (Stable)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.5.3%22+). - [fixed issues query for Typescript 4.5.4 (Stable)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.5.4%22+). - [fixed issues query for Typescript 4.5.5 (Stable)](https://togithub.com/microsoft/TypeScript/issues?q=milestone%3A%22TypeScript+4.5.5%22+). Downloads are available on: - [npm](https://www.npmjs.com/package/typescript)

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 WhiteSource Renovate. View repository job log here.