@vue/tsconfig
Advanced tools
Comparing version 0.2.0 to 0.3.0
{ | ||
"name": "@vue/tsconfig", | ||
"version": "0.2.0", | ||
"version": "0.3.0", | ||
"description": "A base TSConfig for working with Vue.js", | ||
@@ -5,0 +5,0 @@ "main": "tsconfig.json", |
@@ -28,6 +28,3 @@ # `@vue/tsconfig` | ||
```json | ||
"extends": [ | ||
"@vue/tsconfig/tsconfig.json", | ||
"@vue/tsconfig/tsconfig.dom.json" | ||
] | ||
"extends": "@vue/tsconfig/tsconfig.dom.json" | ||
``` | ||
@@ -60,11 +57,3 @@ | ||
- The usage of base `tsconfig.json` is unchanged. | ||
- `tsconfig.web.json` is now renamed to `tsconfig.dom.json`, to align with `@vue/runtime-dom` and `@vue/compiler-dom`, and it only contains dom-specific options, you need to use it in conjunction with the base `tsconfig.json`: | ||
```json | ||
"extends": [ | ||
"@vue/tsconfig/tsconfig.json", | ||
"@vue/tsconfig/tsconfig.dom.json" | ||
] | ||
``` | ||
- `tsconfig.web.json` is now renamed to `tsconfig.dom.json`, to align with `@vue/runtime-dom` and `@vue/compiler-dom`. | ||
- `tsconfig.node.json` is removed, please read the [Node.js section](#configuration-for-node-environments) above for Node.js usage. | ||
@@ -75,3 +64,3 @@ | ||
- `moduleResolution` changed from `node` to [`bundler`](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#moduleresolution-bundler) | ||
- The `lib` option in `tsconfig.dom.json` now includes `ES2020` by default. | ||
- The `lib` option in `tsconfig.dom .json` now includes `ES2020` by default. | ||
- Previously it was ES2016, which was the lowest ES version that Vue 3 supports. | ||
@@ -83,6 +72,3 @@ - Vite 4 transpiles down to ES2020 by default, this new default is to align with the build tool. | ||
{ | ||
"extends": [ | ||
"@vue/tsconfig/tsconfig.json", | ||
"@vue/tsconfig/tsconfig.dom.json" | ||
], | ||
"extends": "@vue/tsconfig/tsconfig.dom.json", | ||
"compilerOptions": { | ||
@@ -89,0 +75,0 @@ "lib": ["ES2016", "DOM", "DOM.Iterable"] |
{ | ||
"extends": "./tsconfig.json", | ||
"compilerOptions": { | ||
@@ -3,0 +4,0 @@ "lib": [ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Deprecated
MaintenanceThe maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.
Found 1 instance in 1 package
59
0
6522
75