@gjsify/rolldown-plugin-vue 0.52.0 → 0.54.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.
- package/README.md +1 -1
- package/lib/index.js +1 -1
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -98,7 +98,7 @@ Rolldown picks a parser from the id's extension, and `.vue` is not one it knows:
|
|
|
98
98
|
|
|
99
99
|
So this plugin renames. `resolveId` resolves `./App.vue` normally (`skipSelf`) and appends `.ts` to the absolute path; `load` strips the suffix, reads the real file and compiles it. The real path stays the id's prefix, so a diagnostic still names the file.
|
|
100
100
|
|
|
101
|
-
`moduleType` is not an undocumented field — rolldown 1.1.4 ships it in `SourceDescription`, and it is the *designed* mechanism. It is unavailable here because `@gjsify/rolldown-native`'s `plugin_proxy.rs::parse_module_type` accepts `js`/`ecmascript`/`json`/`text` and rejects everything else, which makes it unusable on the primary target. That gap is recorded in `status/open-todos.md`; closing it is a prebuild-cycle change and this plugin does not depend on it.
|
|
101
|
+
`moduleType` is not an undocumented field — rolldown 1.1.4 ships it in `SourceDescription`, and it is the *designed* mechanism. It is unavailable here because `@gjsify/rolldown-native`'s `plugin_proxy.rs::parse_module_type` accepts `js`/`ecmascript`/`json`/`text` and rejects everything else, which makes it unusable on the primary target. That gap is recorded in `status/open-todos/README.md`; closing it is a prebuild-cycle change and this plugin does not depend on it.
|
|
102
102
|
|
|
103
103
|
One suffix and not four is why `lang="jsx"`/`"tsx"` is refused. A `<script>` with no `lang` is therefore parsed as TypeScript — harmless except for the handful of JS/TS syntactic ambiguities, and `lang="ts"` is what a project using this type surface writes anyway.
|
|
104
104
|
|
package/lib/index.js
CHANGED
|
@@ -16,7 +16,7 @@
|
|
|
16
16
|
// target. So this plugin renames the module id in `resolveId` and compiles in
|
|
17
17
|
// `load`, which is the only one of the three candidates measured working on BOTH
|
|
18
18
|
// engines. The table of what each did is in the README; the core gap is recorded in
|
|
19
|
-
// `status/open-todos.md`.
|
|
19
|
+
// `status/open-todos/README.md`.
|
|
20
20
|
//
|
|
21
21
|
// Everything else worth knowing is at its call site, because each one is a way this
|
|
22
22
|
// compiles green and renders wrong.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gjsify/rolldown-plugin-vue",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.54.0",
|
|
4
4
|
"description": "Vue 3 single-file-component compiler plugin for Rolldown / Rollup / Vite — targeting a gjsify custom renderer",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "lib/index.js",
|
|
@@ -57,9 +57,9 @@
|
|
|
57
57
|
}
|
|
58
58
|
},
|
|
59
59
|
"devDependencies": {
|
|
60
|
-
"@gjsify/cli": "^0.
|
|
61
|
-
"@gjsify/rolldown-plugin-deepkit": "^0.
|
|
62
|
-
"@gjsify/unit": "^0.
|
|
60
|
+
"@gjsify/cli": "^0.54.0",
|
|
61
|
+
"@gjsify/rolldown-plugin-deepkit": "^0.54.0",
|
|
62
|
+
"@gjsify/unit": "^0.54.0",
|
|
63
63
|
"@types/node": "^25.9.2",
|
|
64
64
|
"rolldown": "^1.1.4"
|
|
65
65
|
},
|