vize 0.350.2 → 0.352.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +15 -10
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -193,14 +193,15 @@ Use the Rust CLI when you need Corsa project diagnostics across Vue, TS, TSX, an
193
193
 
194
194
  `vize ready` runs `fmt --write`, `lint`, `check`, and `build` in that order.
195
195
 
196
- ## Experimental TypeScript Content Mapper
196
+ ## TypeScript Content Mapper
197
197
 
198
198
  The TypeScript 7.1
199
199
  [API roadmap](https://github.com/microsoft/typescript-go/issues/4830) identifies Content Mappers as
200
200
  the TS Server plugin replacement needed by Vue. Vize publishes the package metadata and protocol
201
- server proposed by [microsoft/typescript-go#4712](https://github.com/microsoft/typescript-go/pull/4712),
202
- letting a compatible `tsgo` build transform `.vue` files directly instead of materializing a
203
- parallel `.vue.ts` project.
201
+ server merged upstream in
202
+ [microsoft/typescript-go#4712](https://github.com/microsoft/typescript-go/pull/4712),
203
+ letting a `tsgo` build with content-mapper support transform `.vue` files directly instead of
204
+ materializing a parallel `.vue.ts` project.
204
205
 
205
206
  ```json
206
207
  {
@@ -222,12 +223,16 @@ parallel `.vue.ts` project.
222
223
  tsgo --runExternalCode --noEmit -p tsconfig.json
223
224
  ```
224
225
 
225
- The content-mapper API is not in a released TypeScript native preview yet. Use the exact PR build
226
- while evaluating it, keep `--runExternalCode` explicit, and keep `vize check` as the supported
227
- typecheck path until TypeScript ships the protocol. Vize currently negotiates protocol v1 with
228
- UTF-8 mappings, declares its `noUnusedLocals` compiler-option dependency under the
229
- `typescript.contentMapper` manifest key, and tags every transform response with the `.tsx` virtual
230
- extension so both TypeScript and embedded JSX parse correctly.
226
+ Content Mappers are merged on the `typescript-go` main branch but are not in a released TypeScript
227
+ native preview yet. Use a `tsgo` built from main while evaluating them, keep `--runExternalCode`
228
+ explicit, and keep `vize check` as the supported typecheck path until a native preview release
229
+ ships the protocol. Vize negotiates protocol v1 with UTF-8 mappings, resolves its mapper options
230
+ and its declared `noUnusedLocals` compiler-option dependency per project through the
231
+ `openProject`/`closeProject` lifecycle (invalid options surface as `optionDiagnostics` in the
232
+ tsconfig), maps `<!-- @vue-expect-error -->` and `<!-- @vue-ignore -->` template comments onto
233
+ the protocol's diagnostic directives, and tags every transform response with the `.tsx` virtual
234
+ extension so both TypeScript and embedded JSX parse correctly. See the
235
+ [Content Mapper guide](https://vizejs.dev/guide/content-mapper) for setup and directive semantics.
231
236
 
232
237
  ## Compiler and Tool Options
233
238
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "vize",
3
- "version": "0.350.2",
3
+ "version": "0.352.0",
4
4
  "description": "Vize - High-performance Vue.js toolchain in Rust",
5
5
  "keywords": [
6
6
  "cli",
@@ -53,7 +53,7 @@
53
53
  "access": "public"
54
54
  },
55
55
  "dependencies": {
56
- "@vizejs/native": "0.350.2",
56
+ "@vizejs/native": "0.352.0",
57
57
  "oxc-transform": "0.144.0"
58
58
  },
59
59
  "devDependencies": {