Add non-built addon flag to Detailed design#16
Merged
NullVoxPopuli merged 1 commit intoNullVoxPopuli:v2-addon-by-defaultfrom Apr 9, 2026
Merged
Conversation
The blueprint should support a flag (e.g. --no-build) for generating simpler addons intended for local/workspace use. These skip the publish build, point exports at source, and drop unneeded devDependencies. 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
Adds a "Non-Built Addons" section to the Detailed design stating that the blueprint should support a flag (e.g.
--no-build) for generating simpler addons intended for local/workspace use.These skip the publish build entirely — no Rollup, no publish babel/tsconfig, no dist directory — and point
exportsat source files. The consuming app's Vite/Embroider build handles transpilation.The exact flag name is left as an implementation detail of the addon-blueprint. The RFC just establishes that this should be a first-class path, since local/workspace addons are common and shouldn't require manually stripping down a full publishable scaffold.
Addresses feedback from ef4 and void-mAlex on emberjs#985.
Test plan
🤖 Generated with Claude Code