feat: stable v2 native plugins #483
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
2 times, most recently
from
ecc5731 to
165a101
Compare
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
12 times, most recently
from
097a16d to
747c24e
Compare
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
7 times, most recently
from
ce51c11 to
9ee6920
Compare
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
6 times, most recently
from
dba3281 to
d6b9c56
Compare
shulaoda
commented
Dec 3, 2025
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
from
d6b9c56 to
6eddf7b
Compare
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
from
6eddf7b to
689f9ba
Compare
shulaoda
commented
Dec 3, 2025
| renderBuiltUrl: undefined, | ||
| hmrPartialAccept: false, | ||
| enableNativePlugin: process.env._VITE_TEST_JS_PLUGIN ? false : 'v1', | ||
| enableNativePlugin: process.env._VITE_TEST_JS_PLUGIN ? false : true, |
Member
Author
There was a problem hiding this comment.
It needs to be reverted before merging.
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
from
689f9ba to
122013a
Compare
shulaoda
commented
Dec 3, 2025
sapphi-red
requested changes
Dec 3, 2025
| case 'v1': | ||
| case true: | ||
| return 1 | ||
| case true: |
Member
There was a problem hiding this comment.
Suggested change
| case true: | |
| case 'v2': | |
| case true: |
We should also update the jsdoc of enableNativePlugin option.
Member
Author
There was a problem hiding this comment.
I'm considering adding a v2 option since the v2 implementation is still experimental and not fully stabilized. My current idea is to treat enableNativePlugin: true as enabling v2, while the default behavior continues to use v1. 🤔
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
2 times, most recently
from
f627dd0 to
4c5f53a
Compare
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
3 times, most recently
from
51dfefc to
0b387c5
Compare
shulaoda
force-pushed
the
10-20-stable-v2-native-plugins
branch
from
0b387c5 to
97a4abe
Compare
Member
Author
|
@sapphi-red Could you help me trigger the ecosystem CI? It seems I don’t have permission to do it. |
Member
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
If you want to enable these new native plugins, you need to set
enableNativePlugin: true, the default value is'v1'. The v2 native plugins includeassetPlugin,assetImportMetaUrlPlugin,cssPlugin,htmlPlugin, andhtmlInlineProxyPlugin.In addition, the v2 update also improves
nativeBuildImportAnalysisPluginandnativeManifestPlugin. These changes fix the execution order mismatch betweentransformandtransform_asthooks, which previously prevented user plugins from running after built-in plugins even withpostenforcement, making it impossible to access the fully processed code (#373).Note
There may be a slight performance overhead since v2 plugins parse modules individually instead of reusing the AST from
transform_ast. However, the impact should be minimal due to filtering logic that skips unnecessary parsing.