feat: scope the package as @webship/diffy-steps at 2.0.0 (#1) - #2
Merged
Conversation
"name": "diffy-steps", -> "name": "@webship/diffy-steps", "version": "0.1.0", -> "version": "2.0.0", The scope puts the package in the organisation's namespace instead of the global one. The version aligns the plugin with the line it plugs into: it peers against webship-js ^2.0.4, its branch is 2.0.x, and its step phrasings are the 2.0.x phrasings extracted from webship-js. 0.1.0 implied a pre-release on an unrelated track. Scoped packages publish as `restricted` by default, which would contradict the public repository, so publishConfig.access is set to public. Every reference to the package name follows: the install commands, the node_modules/@webship/diffy-steps/... require paths in the configuration examples, the copy and uninstall snippets, the doc headings, and the step-file header. package-lock.json regenerated. Not published. The webship org does not yet exist on npmjs.com and the publishing account needs membership in it before a first release. Verified: npm pack --dry-run reports @webship/diffy-steps@2.0.0, and the suite still passes 6 scenarios / 37 steps against the mock Diffy API. Co-Authored-By: Claude Opus 5 <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
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.
Scopes the package and moves it onto the 2.0.x line.
Closes #1
Why 2.0.0
The plugin peers against
webship-js ^2.0.4, its branch is2.0.x, and its stepphrasings are the 2.0.x phrasings extracted from webship-js.
0.1.0implied apre-release with no compatibility promise and put the plugin on a version track
unrelated to the harness it plugs into.
One addition beyond the rename
Scoped packages publish as
restrictedby default. Without this,npm publishwould either fail or publish privately — contradicting the now-public
repository. Flagging it because it was not in the request but the rename is
incomplete without it.
Everything that follows the name
README.mdrequire:pathdocs/README.mdtests/step-definitions/README.mdrequire:path,cpsnippet, uninstall snippettests/step-definitions/diffy.steps.jspackage-lock.jsonThe consumer
require:path becomes:'node_modules/@webship/diffy-steps/tests/step-definitions/**/*.js'GitHub URLs (
github.com/webship/diffy-steps) and the directory name areunchanged — only the npm package identity moved.
Before publishing — two prerequisites outside this repo
webshiporg must exist on npmjs.com.https://registry.npmjs.org/-/org/webshipreturns 404 today, andnpm publishwill fail on a scope with no org behind it.Still unpublished, as intended.
Test notes
npm pack --dry-run→@webship/diffy-steps@2.0.0, filenamewebship-diffy-steps-2.0.0.tgz, same 5-file payload.package.jsonre-parsed through Node after editing — valid, key order preserved, non-ASCII intact.One knock-on outside this repository: webship-js PR
#303 documents the unscoped
node_modules/diffy-steps/...path. It needs the scoped path before it merges —handled separately so this PR stays single-purpose.
AI-Generated: Yes (applied the rename and version bump and updated every
reference; reviewed by Rajab Natshah.)
Checkpoints
Automated unit/functional testing coverage