feat: v2 addons #9407
Merged
feat: v2 addons #9407
Conversation
This file contains 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
runspired
added
🎯 canary
16 tasks
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.
monitoring to see if v2 addons are feasible yet
In our work in #9292 we discovered that
.d.ts) is not yet feasible, thoughdts-buddyapproach was not yet explored (vite, rollup, tsc, and api-extractor approaches were)We merged the big PR with all the work but turned off type rollup and configured most of the packages to continue to ship as v1 addons with a simple switch to upgrade them to v2 if possible. This PR triggered that switch so that we can debug these issues.