[ryansolid]

Summary

This adds a frontends option. A language that lowers to Solid can claim a file extension and compile its own modules:

solid({ frontends: { ".x": x() } })

.rx (ReactiveScript) is built in. If the project has @reactivescript/compiler installed, .rx modules compile with plain solid().

• The plugin resolves @reactivescript/compiler/vite from the project root the first time it meets an .rx module. A project without .rx files never loads it.
• If the package is missing, the module fails with an install hint. The load is retried on the next .rx module, so installing the package fixes a running server.
• A .rx entry in frontends replaces the built-in one.

A front end implements compile(source, { id, moduleId, ssr, root, solid, addWatchFile }) and returns { code, map?, css? }, or null to pass the module through.

• id is the file path. moduleId is the full id with its query, so a front end that imports its own modules under a query (e.g. ./x.rx?rx-dep) can tell the forms apart.
• solid holds the compiler options this plugin would use for a JSX module in that environment (generate, hydratable, moduleName, dev, …), so a front end that ends in @solidjs/compiler compiles the same way.

The result then takes the lowered .tsrx route:

• the lazy and HMR refresh passes;
• server functions, with IDs from the module's real path;
• css as a CSS module (?solid-tsrx-css), including on hot update;
• dep scanning (optimizeDeps.extensions);
• source maps combined back to the front end's map.

Solid's own extensions can't be claimed. Today extensions parses its files as JSX text, which a language with its own syntax can't use, and .tsrx is routed by name.

What changed:

• src/index.ts: the types, validation and routing, and the lazily loaded built-in .rx.
• src/server-functions/index.ts: front-end extensions are included, and lowered modules are handled after Solid's pass.
• src/tsrx.ts: the CSS query alone identifies the stylesheet module.
• A README section and a changeset.

Dependency: server functions in front-end modules need solidjs/solid#4320, which is merged and will ship in the next compiler release. That test is skipped until then (the directivesTakeAnyExtension() probe).

Testing

• New src/frontends.test.ts uses a .fe front end. It covers:
  • client dom compile and SSR;
  • the CSS module import and load;
  • map sources;
  • the queried moduleId;
  • addWatchFile;
  • refusing .tsx;
  • server functions.
• It also covers built-in .rx, against a stub @reactivescript/compiler in a temp project, plus the install hint when the package is missing. 10/10 pass.
• The full unit suite passes, 46/46, with #4320's compiler linked in. tsc --noEmit is clean.
• End to end: @reactivescript/compiler (a Node-API build of ReactiveScript's compiler, Rust crate: front half, resolved model (CP-6), lowering through compile_program, and @reactivescript/compiler ryansolid/reactivescript#6) builds all 12 example apps through plain solid() with Vite 8.
  • Each app is driven in Chromium. The todo app also runs under the dev server.
  • A page with two programs that share a module bundles that module once.
  • 14 pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_0117BoWMdD4K7882vob4J9vq

[changeset-bot]

🦋 Changeset detected

Latest commit: b8cc5fe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@solidjs/vite-plugin	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@solidjs/vite-plugin@471

commit: b8cc5fe