Tidy up publish readiness after the scope rename#45
Merged
Conversation
Follow-up from the npm publish prep: - Regenerate package-lock.json root entry, which still carried the old unscoped name and ISC license. - Add publishConfig.access=public so scoped publishes don't silently go private (and don't need a manual --access flag each time). - Add a bugs URL. - Mark bin/reglance.mjs executable. Co-Authored-By: Claude Opus 4.8 (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.
Summary
Follow-up cleanup found during a post-publish review. None of these change runtime behavior; they close loose ends left by the rename to
@happyprime/reglanceand harden future publishes.package-lock.jsonroot entry — it still carried"name": "reglance"and"license": "ISC", out of sync withpackage.json.npm ciwould otherwise see a mismatch.publishConfig.access: public— scoped packages default to restricted, so every publish needed a manual--access publicand could silently go private. This makes public the default.bugsURL — points issue reporters at the GitHub tracker.chmod +x bin/reglance.mjs— was mode 644; executable in a fresh clone now (npm already set this in the published tarball, so installed consumers were unaffected).Verification
npm test→ 83 pass@happyprime/reglance/MITpublishConfigandbugspresent; bin is755🤖 Generated with Claude Code