fix(deps): pin @nexssp/os to exactly 2.0.36 (broken consumer installs) - #28
Merged
Conversation
^2.0.36 resolves to 2.1.1 on fresh installs; 2.1.x tarballs lack legacy.mjs that their exports map references, so the CLI crashes at startup for every consumer. Reproduced by installing the published 0.1.1 into a clean prefix; fixed by the exact pin.
Merged
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.
Problem
The published
@arcasilesgroup/ai-shell@0.1.1is broken for fresh installs:"@nexssp/os": "^2.0.36"lets npm resolve 2.1.1, whose published tarball is missinglegacy.mjswhile its own exports map points at it (upstream packaging bug — already ignored for dependabot in #19). Our own CI never caught it because the committed lockfile held 2.0.36; consumers get the range.Fix
Exact pin
2.0.36+ changeset (patch → 0.1.2).Verification (from the registry, clean prefix)
@nexssp/oswas 2.1.1ai --version→0.1.1OKjust build lint test securitygreen, contract check passes, 0 vulnerabilities