ReScript plugin with build orchestration server integration

[hyperpolymath]

Hi Vite team,

I'm working on a Vite plugin for ReScript called rescript-vite that takes a different approach from the existing @jihchi/vite-plugin-rescript:

• Written entirely in ReScript (no TypeScript dependency) — the plugin itself compiles from .res to JS
• Integrates with a build orchestration server (BoJ SSG-MCP) for cross-project build caching and coordination
• Uses Deno as runtime instead of Node/npm
• Full diagnostic parsing, HMR for .res/.resi files, and error overlay support via Vite's WebSocket API
• Comprehensive test suite (40+ tests, 22 benchmarks)

The repo is at hyperpolymath/rescript-vite.

I'd like to understand what it would take for this variant to work well alongside the existing JS/TS tooling in Vite's ecosystem. Specifically:

1. Are there any plugin API conventions or patterns I should follow to ensure smooth interop with other Vite plugins?
2. Would the team be open to reviewing this for potential inclusion in the official plugins directory or awesome-vite?
3. Any guidance on how ReScript's compilation model (separate compiler process producing .res.js files) interacts with Vite's module graph — am I handling HMR correctly by looking up the .res.js companion file?

Happy to take feedback and adjust the implementation. Thanks for building such a great tool.

[aniruddhaadak80]

@hyperpolymath

Vite is usually blazingly fast, but issues like this often crop up around dependency pre-bundling or rollup configurations.

1. Pre-bundling: Try deleting your node_modules/.vite cache and running npm run dev -- --force to make Vite rebuild the dependencies.
2. Externalizing Modules: If you are seeing issues where built-in node modules (like "stream" or "path") are breaking, it is because Vite is primarily a frontend build tool. You might need to add polyfills via vite-plugin-node-polyfills or explicitly externalize it in build.rollupOptions.external.

Let me know if clearing the Vite cache or tweaking the Rollup config gets you past this hurdle.

Hope this points you in the right direction! Let me know how it goes. Happy coding!