Skip to content

Publish @anonvote/crypto to npm — package does not exist on the registry #17

Description

@grantfox-oss

The README shows an npm version badge linking to
npmjs.com/package/@anonvote/crypto but the package
does not exist on npm. The badge is broken. core lists
@anonvote/crypto as a dependency but any contributor
running npm install in core hits a missing package
error immediately. The package.json has prepublishOnly
configured to run build and test before publish and
the version is at 1.4.0 — publish was clearly intended
but never completed.

PR #11 is open and unmerged, aligning the crypto
primitives with the type spec. Publish must not happen
until that PR is reviewed.

Scope:

  • Review and merge or close PR feat: align crypto primitives with @anonvote/crypto type spec #11 before publishing
  • Confirm npm run build produces a clean dist/ with
    correct .js and .d.ts outputs for all exports
  • Confirm npm test passes with no failures
  • Create the @AnonVote npm org if it does not exist
  • Publish to npm — npm publish --access public
  • Verify the README badge resolves after publish
  • Update core's package.json to reference the
    published version

Acceptance Criteria:

  • PR feat: align crypto primitives with @anonvote/crypto type spec #11 reviewed before publish
  • npm run build produces clean dist/ with no errors
  • npm test passes with no failures
  • @anonvote/crypto visible at npmjs.com/package/@anonvote/crypto
  • npm install @anonvote/crypto works from a fresh directory
  • README badge resolves with the correct version
  • core's package.json updated to use the published package

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial CampaignCampaign: Official CampaignbugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions