-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using Rolldown with Vite v6 #43
base: main
Are you sure you want to change the base?
Conversation
1d231ee
to
2087832
Compare
259bd2a
to
6af67ee
Compare
FYI,
this is by design, if use customResolver in native plugin, there is no performance difference between |
for all |
@IWANABETHATGUY I've made reproductions for the cases other than resolve plugin related ones. (I'm going to make for the resolve related ones now.) |
I fixed the import-meta glob reproduction; it was using |
Can you file these issues on rolldown? |
Made the reproductions for resolve related ones.
Did you mean to quote #43 (comment) instead of #43 (comment), right? |
Sorry, yeah I mean #43 (comment) |
Done 👍 I didn't make an issue for "manifest: cannot use data on Vite side (e.g. css/assets) and needs to be environment-specific" and "does not support vitejs#12786 (reproduction, expected to have console.log preserved in the output)" for now as I'm not sure what the next step is and the issue will be opaque / unactionable. |
Co-authored-by: underfin <[email protected]>
Co-authored-by: underfin <[email protected]>
Co-authored-by: underfin <[email protected]>
Co-authored-by: underfin <[email protected]>
2cf0eb2 fe71cbc Co-authored-by: IWANABETHATGUY <[email protected]>
Co-authored-by: IWANABETHATGUY <[email protected]>
066d276
to
04c717f
Compare
Description
Applied changes from #24 and #27 to the main branch after the environment API PR is merged.
Also fixed errors on Windows and cleaned up some unneeded changes.
#24 implemented build-time dep optimization partially, but I didn't include that change in this PR.
e2e test status
-rolldown/rolldown#2031
- using Array input generate name is not expected, the entry name will be like index~1.js
missing feature list that was supported by esbuild / rollup
options.watch
watcher.on('event', listener)
shouldTransformCachedModule
,watchChange
,closeWatcher
this.addWatchFile
meta
on module info: this can be workarounded as it's not part of the public APIumd
formatsystem
formatoutput
is currently an object instead of an arrayoptions.attributes
forresolveId
hookSourceMap
type does not supporttoString
andtoUrl
: not necessary but better for easier migrationresolveImportMeta
hook: can usetransform
hook for Vite's usecaseoptions.preserveEntrySignatures
: not necessary but nice for smaller bundlesimprovements needed later on Vite side
optimizeDeps.esbuildOptions
intooptimizeDeps.rollupOptions
automatically if possiblenative plugin incompatibilities
customResolver
optionplayground/backend-integration
, you can see the manifest not containingcss
andassets
field inindex.html
..replaceAll('\\', '/')
on the resolved id (reproduction [windows only])console.log
preserved in the output)TODO list for me
nativeBuildImportAnalysisPlugin
option: f92519b#diff-121079017d1fa98d6a0ea3354d5c73df45ab277078228cd7384c7a4e84c5a813R182bundle
: https://github.com/vuejs/vitepress/blob/68150a6f3349c1741ed5683e3010d9ecea02f3a8/src/node/plugin.ts#L353-L362