feat: add @plexus-ms/config shared tool-config package - #10
Merged
Conversation
Ships biome.json behind an './biome' export for one-line extends
("root": false so in-repo dogfooding doesn't collide with the root
config). The repo's own root config now extends it.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Tool configs share one audience and one release cadence, so they ship as one package (@plexus-ms/config/biome, later /tsconfig, ...) — one npm bootstrap and one trusted publisher instead of one per config. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
davidjalbers
changed the title
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
1 participant
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.
Adds
@plexus-ms/config: shared tool configurations as subpath exports, starting with Biome —"extends": ["@plexus-ms/config/biome"](§ 9 PLX). Configs share one audience and one release cadence, so they bundle into one package (one bootstrap publish, one trusted publisher); a config would split out only if it ever grows its own cadence. The repo's own rootbiome.jsonextends it (dogfood), which also verifies the consumer path.Bootstrap caveat applies (see manual): the first publish must be manual, then register the trusted publisher for the new package.
🤖 Generated with Claude Code