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
v3+: Can we use "node:<buildinName>" as import specifier in v3+? #4595
Comments
I put it into #4596 |
This issue has been resolved via #4596 as part of rollup@3.0.0-4. Note that this is a pre-release, so to test it, you need to install Rollup via |
This issue has been resolved via #4596 as part of rollup@3.0.0-5. Note that this is a pre-release, so to test it, you need to install Rollup via |
This issue has been resolved via #4596 as part of rollup@3.0.0-6. Note that this is a pre-release, so to test it, you need to install Rollup via |
This issue has been resolved via #4596 as part of rollup@3.0.0-7. Note that this is a pre-release, so to test it, you need to install Rollup via |
This issue has been resolved via #4596 as part of rollup@3.0.0-8. Note that this is a pre-release, so to test it, you need to install Rollup via |
This issue has been resolved via #4596 as part of rollup@3.0.0. You can test it via |
Expected Behavior / Situation
i type something like
and get all nodejs buildin modules that are required by the module
Actual Behavior / Situation
i write the command and i get nothing
Modification Proposal
Target Branch
The text was updated successfully, but these errors were encountered: