chore: standardize on npm, remove yarn.lock#221
Merged
sameh-farouk merged 21 commits intoJun 3, 2026
Conversation
sameh-farouk
force-pushed
the
master-update-compose-stacks
branch
from
a8363a8 to
3ae18d2
Compare
sameh-farouk
force-pushed
the
master-standardize-npm
branch
from
c32d9ee to
26a6867
Compare
CI and local dev used yarn (yarn.lock) while the Dockerfile used npm ci (package-lock.json). The two lock files had 57 version mismatches. Standardize on npm everywhere: - Remove yarn.lock - Regenerate package-lock.json from clean npm install - CI: yarn install -> npm ci, yarn build -> npm run build - docker-compose: ["yarn", "process"] -> ["npm", "run", "process"] - Docs and scripts: yarn -> npm run Fixes: #220 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
sameh-farouk
force-pushed
the
master-update-compose-stacks
branch
from
3ae18d2 to
be49aed
Compare
sameh-farouk
force-pushed
the
master-standardize-npm
branch
from
26a6867 to
1e38c20
Compare
…ith license reference
feat: automate type generation with append-only version log
fix: resolve data loss bugs in farm IP, node interface, and contract mapping handlers
fix: resolve logic issues in contract and farm mapping handlers
cleanup: remove dead code, unused imports, and extract certification helpers
fix: read node certification from NodeStored event payload
# Conflicts: # README.md
docs: update all project documentation
perf: add database indexes to commonly queried entity fields
chore: update compose stacks and shared networking
# Conflicts: # README.md
This was referenced Jun 3, 2026
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
2 participants
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
Fixes #220
CI and local dev used yarn (
yarn.lock) while the Dockerfile usednpm ci(package-lock.json). The two lock files had 57 version mismatches, meaning CI and local dev ran against different dependency versions than production Docker images.Changes
yarn.lockpackage-lock.jsonfrom cleannpm installyarn install->npm ci,yarn build->npm run build["yarn", "process"]->["npm", "run", "process"]yarn->npm runTest plan
npm ciinstalls cleanly from the new lock filenpm run buildpasses