Silence prefer builtins and circular dependency warnings when building extensions #18366
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.
Those warnings come up when bundling API extensions. Circular dependency warnings are only silenced when only external files are involved. Unfortunately, the prefer builtins warning can't be disabled for external files only, enabling the option and thus silencing the warning should still be rasonably safe for API extensions as this is rollup's default.