Keep npm out of the workspace when publishing - #12
Merged
Conversation
Third dry run failed with EUNSUPPORTEDPROTOCOL again, in the same place, after the reorder. The reorder was not wrong, it was insufficient. Any npm command run inside packages/relic-mcp walks up to the workspace root and resolves the sibling packages, and those still carry bun's `workspace:*`. Stripping this package's own manifest never had a chance, because the manifests npm chokes on belong to @relic/format, @relic/ server, and @relic/viewer. Two changes. `npm version` is replaced by a direct JSON edit, which sets the version and drops devDependencies in one pass and resolves nothing. And every remaining npm invocation carries --no-workspaces, so pack and publish stop climbing out of the package they were pointed at. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Third dry run failed with
EUNSUPPORTEDPROTOCOLagain, in the same step, after the reorder. The reorder wasn't wrong, it was insufficient.Any npm command run inside
packages/relic-mcpwalks up to the workspace root and resolves the sibling packages, and those still carry bun'sworkspace:*. Stripping this package's own manifest never had a chance, because the manifests npm chokes on belong to@relic/format,@relic/server, and@relic/viewer.Two changes:
npm versionis replaced by a direct JSON edit, which sets the version and dropsdevDependenciesin one pass and resolves nothing.--no-workspaces, sopackandpublishstop climbing out of the package they were pointed at.🤖 Generated with Claude Code