Replies: 1 comment
-
Rolldown may support it but the priority won't be high (as you know, it's a legacy format). If you'd like to see it become a built-in feature, adding a "👍" reaction to rolldown/rolldown#2528 would help. That said, you should be able to transform ESM to AMD using a plugin like rolldown/rolldown#2387 (comment). For AMD inputs, I guess that |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋
First of all, thank you for the great work on rolldown-vite — it's exciting to see the performance improvements coming from Rust-based tooling!
I was wondering if there are any plans to support the AMD (Asynchronous Module Definition) format in the future? While AMD is less common in modern workflows, some legacy systems and integrations still rely on it.
Rollup itself supports AMD via its output.format: 'amd' configuration option, and there are plugins like rollup-plugin-amd or custom setups that help with transforming or bundling AMD modules.
Would it be feasible to consider AMD support in rolldown-vite, either natively or via a plugin interface? Or is the focus strictly on modern formats like ESM and CJS?
Beta Was this translation helpful? Give feedback.
All reactions