Add in-repo addons migration path to RFC #985#15
Merged
NullVoxPopuli merged 1 commit intoNullVoxPopuli:v2-addon-by-defaultfrom Apr 9, 2026
Merged
Conversation
Address ef4's review comment that the RFC should explain what to do about in-repo addons. They can be converted to v2 by establishing them as real package dependencies via workspace features, and they'll typically be "unbuilt" addons pointing exports at source files. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
NullVoxPopuli
approved these changes
Apr 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Addresses ef4's review comment on emberjs#985 that the RFC should explain what to do about in-repo addons.
lib/in-repo addons are v1 constructsTest plan
🤖 Generated with Claude Code