build(deps): update dependency @softwareventures/tsconfig to v8 (main) #100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.3.0
->8.1.0
Release Notes
softwareventures/tsconfig (@softwareventures/tsconfig)
v8.1.0
Compare Source
Features
v8.0.0
Compare Source
⚠ BREAKING CHANGES
ES2020. This breaks compatibility with obsolete
versions of Node and obsolete browsers. If you
need to support these older systems either
override
compilerOptions.target
or use Babelto compile down to older ES syntax.
option is no longer set. This option is not
appropriate for most projects. It should only be
set for projects that are transpiled using Babel
(or similar). See
https://www.typescriptlang.org/tsconfig#allowSyntheticDefaultImports
longer set, meaning TypeScript will no longer
exclude type declarations for code marked
@internal
. This option was unsafe becauseTypeScript does not check that the resulting
declarations are valid. Projects that relied on
this option should consider using api-extractor
(https://api-extractor.com/) instead, or override
this option to true in their tsconfig.
longer included in the compilation by default
(tsconfig specifies the option
"types": []
).Consuming projects that require ambient types
should list them explicitly in their tsconfig.
For example, projects that target node should
add a dependency on @types/node and specify
{"compilerOptions": {"types": ["node"]}}
.webworker-commonjs configurations are obsolete
and have been removed. Instead of commonjs, use
the top level configuration (replace
"@softwareventures/tsconfig/commonjs" with
"@softwareventures/tsconfig"). Instead of
dom-commonjs, use the dom configuration (replace
"@softwareventures/tsconfig/dom-commonjs" with
"@softwareventures/tsconfig/dom"). Instead of
webworker-commonjs, use the webworker
configuration (replace
"@softwareventures/tsconfig/webworker-commonjs"
with "@softwareventures/tsconfig/webworker").
The CommonJS-specific configurations are obsolete
now since the corresponding base configurations
use "Node16" module resolution and compile to
"Node16" modules. This is equivalent to compiling
to CommonJS modules and following CommonJS
resolution rules when that is what node would
expect, and compiling to ES Modules and following
ES Module resolution rules when that is what node
would expect.
compiler error. This usually indicates a broken
attempt to write an object literal.
See https://www.typescriptlang.org/tsconfig#allowUnusedLabels
now raise a compiler error. See
https://www.typescriptlang.org/tsconfig#allowUnreachableCode
dependency on typescript v5.2.2 or later.
Consuming projects should upgrade typescript to
at least that version.
Features
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.