Fix TIA JS module graph for Vue and Svelte projects

[m0shiurX]

What:

• Bug Fix
• New Feature

Description:

bin/pest-tia-vite-deps.mjs runs rolldown over the page files, but none of its three plugins can read a .vue or .svelte file. Every single file component fails to parse, so the build exits non zero:

node vendor/pestphp/pest/bin/pest-tia-vite-deps.mjs .
Error: Build failed with 367 errors:
[PARSE_ERROR] HTML comments are not allowed in modules
[PARSE_ERROR] Unexpected JSX expression

JsModuleGraph::resolve() swallows that, so build() hands Tia.php an empty map on every run and buildStrict() shows the Vite resolver unavailable warning. TIA keeps working, it just loses all frontend precision for the whole Inertia layer, silently, on every Laravel + Inertia + Vue project.

The fix is a load hook that returns the component's <script> blocks in place of the raw file. Every import edge lives in a script block, so the graph is the same one the real compiler would produce, with no framework plugin, no new dependency and no compile step. That matches how assetStub already stubs CSS and images rather than processing them.

Two more things showed up once the components parsed, and both are in the same helper:

• TypeScript drops an import whose bindings the emitted code never uses. A component that only appears in a <template> is exactly that, so every lang="ts" page came back with zero edges. transform.typescript.onlyRemoveTypeImports keeps the value imports.
• Rolldown no longer bundles CSS, so assetStub has to return moduleType: 'js' for the file it replaces. Without it any page that imports a stylesheet fails the build, single file component or not.

Verified against a real Inertia + Vue app: the helper went from exit 1 with 367 parse errors to exit 0 with a full page map. Tests cover the extraction as a pure function (extractSfcScript) plus an end to end rolldown build over a fixture component tree, skipped when rolldown is not installed.

Two alternatives I did not take. Loading @vitejs/plugin-vue or @sveltejs/vite-plugin-svelte from the project's node_modules means resolving and version matching arbitrary plugins and pulling a full component compile into a pre pass that is meant to be fast, for output the graph never reads. Importing the project's vite.config.* and reusing its plugins is something the file already rejects on purpose, see the comment above loadAliasFromViteConfig().