Rolldown-Vite

[sapphi-red]

Description

Current Status

• Vite repo test status
  • ✅ unit tests
  • e2e tests
    • ✅ assets: skipping watch related tests
    • ✅ external: changed the test for intended behavior change
    • ❌ legacy: system output is not supported yet
    • ⚠️ object-hooks: sequential: false object hooks are not supported
    • ⚠️ optimize-deps: some tests skipped in build due to [Feature Request]: The behavior of dynamic import a cjs module rolldown/rolldown#2031
    • ✅ resolve: skipped some browser field related tests as those cases were only supported by esbuild and Vite, also skipped some test that does fallback based on the file content which is Vite only and I believe it should not be done
• ecosystem-ci (see https://github.com/vitejs/vite-ecosystem-ci/blob/rolldown-vite/README-temp.md)

Intended behavior differences

• esbuild needs to be installed manually in the following cases:
  • when using build.minify: 'esbuild'
  • when using a plugin using transformWithEsbuild function
• process.env.ROLLDOWN_OPTIONS_VALIDATION = 'loose' may need to be set to allow options not supported by rolldown
• passing the same browser with multiple versions of it to build.target errors: esbuild selects the latest version of it, but that's probably what you intend
• transformer: define does not share reference for objects oxc-project/oxc#7641
• require is never transformed into import, users needs to inject a polyfill on their own, see f4c3629
• build.rollupOptions.output.manualChunks is not supported. please use build.rollupOptions.output.advancedChunks instead
• splitVendorChunkPlugin is not supported
• structuredClone(bundle) errors with DataCloneError: #<Object> could not be cloned.. please clone it with structuredClone({ ...bundle })

Known missing features

• plugin-legacy
• output.format: 'system' ([Feature Request]: Support for System JS as output format rolldown/rolldown#2387)
• watch mode is only partially working (Build watch mode remaining issues #149)
• resolveImportMeta hook (resolveImportMeta hook implement rolldown/rolldown#1010)
• preserveEntrySignatures option / preserveSignatures in emitFile ([Feature Request]: Support preserveEntrySignatures option / preserveSignatures in emitFile rolldown/rolldown#3500)
• better chunking
  • Less common chunks if rolldown doesn't need to preserve the exports of entires rolldown/rolldown#1842
• dev support with native plugins

related to native plugins

• alias
  • does not support customResolver option
• define
  • per-environment config is not supported yet
• transform
  • does not read tsconfig
  • does not support options
• dynamic import vars
  • does not support resolving with createResolver
• import glob
  • does not support alias
  • does not support subpath imports: https://github.com/rolldown/rolldown/blob/4caa0a93f9ed42bcf9e152c6a4949bacd879b932/crates/rolldown_plugin_import_glob/src/lib.rs#L457
• build-transform
  • does not support options
• manifest
  • cannot use data on Vite side (e.g. css/assets)
    • I cannot make a simple reproduction for this one. If you only enable the native manifest plugin and run build in playground/backend-integration, you can see the manifest not containing css and assets field in index.html

TODO list for me

• setup publish flow
• set rolldown's minify target

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vitejs/rolldown-vite@84

commit: de8164a

[christianjuth]

Found this PR in the Vite docs. Curious how stable rolldown-vite is. On a scale of "Next.js would call this is stable" to "this will actually work 99% of the time", were are we at?

[sapphi-red]

Found this PR in the Vite docs. Curious how stable rolldown-vite is. On a scale of "Next.js would call this is stable" to "this will actually work 99% of the time", were are we at?

I'd say it would work for basic cases as it is passing most tests through out the ecosystem.