-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
feat: support using
for RollupBuild
#5721
feat: support using
for RollupBuild
#5721
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, and also for considering the docs. I have some small comments, especially since to my understanding, no runtime fully supports the feature yet.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5721 +/- ##
=======================================
Coverage 99.00% 99.00%
=======================================
Files 258 258
Lines 8069 8070 +1
Branches 1360 1360
=======================================
+ Hits 7989 7990 +1
Misses 53 53
Partials 27 27 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, this looks good. I still think, though, that it would be nice to have at least a hint in the docs that you can do that. How about in the example, we replace the // create a bundle
comment with something like
// Create a bundle. If you are using TypeScript or a runtime that
// supports it, you can write
//
// await using bundle = await rollup(inputOptions);
//
// instead and do not need to close the bundle explicitly below.
1fd869a
to
d163eb3
Compare
This PR has been released as part of rollup@4.26.0. You can test it via |
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
resolves #5714
Description
Since this is a new
TypeScript
feature, I'm not sure how to add additional test cases on theJavaScript
side.