Skip to content

[Medium] chore(repo): remove package-lock.json (repo uses pnpm) #359

Description

@K1NGD4VID

Context

package-lock.json is committed alongside pnpm-lock.yaml and pnpm-workspace.yaml. Anyone running npm install will produce inconsistent dependency trees.

Where

  • File: package-lock.json
  • Line: 1

Current Behavior

Two lockfiles.

Expected Behavior

Only pnpm-lock.yaml.

Proposed Approach

  1. Delete package-lock.json.
  2. Add package-lock.json to .gitignore.
  3. Consider adding a preinstall script that runs npx only-allow pnpm.

Acceptance Criteria

  • Only one lockfile present
  • npm install fails fast with a clear message

Definition of Done

  • PR links back with Closes #<this-issue-number>.

  • CI is green (both Verify TypeScript Frontend & SDK and Verify Go Indexer & API jobs must pass).

  • Local verification:

  • Markdown renders cleanly on GitHub

  • All internal links resolve

Contributor Tips

  • User-facing docs live under docs/ (GitBook source).
  • Developer setup docs are docs/developer-guide/; protocol docs are docs/protocol/; SDK docs are docs/smart-contracts/.
  • Verify markdown links render on GitHub before pushing (docs/** is picked up automatically).
  • Env-var docs must match the actual keys read by the code -- grep the codebase to confirm.

Tech Stack

docs

How to Claim

Comment .take (or say you're working on it) and open a PR with Closes #<this-issue-number> in the description.

Difficulty: Medium (complexity:medium) -- used for Drips Wave point allocation.

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programchoreMaintenance and non-user-facing cleanupcomplexity:mediumdocumentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions