Why?

• Vite has some codes copied from Rollup and it is harder to keep them consistent.
• It is confusing to have Vite's own system for plugin authors: Access to vite assets meta info by VITE_ASSETS alias #15306, Documenting __VITE_ASSET__ or exposing a function to build asset url. #13459, VITE_ASSET and rollup-replace plugin #17559
• It makes it difficult to create a plugin that works with both Rolldown and Vite. For example, we were not able to extract the wasm plugin part as a rolldown plugin because the asset handling is not aligned.
• It is inefficient to process the code on Vite side while Rolldown can do it
• It makes it easier to support Add support for asset optimization #20360, Hook for optimizing SVGs before inlining them? #19945, Transform references in SVG file #20070

What is needed to done?

Replace __VITE__ASSET__ with Rolldown's import.meta.ROLLUP_FILE_URL_referenceId feature. Find out missing feature on the Rolldown side to achieve that. We may need to figure out whether the distinction of this.emitFile({ type: 'asset' }) and this.emitFile({ type: 'chunk' }) in Rolldown makes sense anymore as moduleTypes feature exists.