Skip to content

chore: standardize on npm, remove yarn.lock (re-target to master)#222

Merged
sameh-farouk merged 2 commits into
masterfrom
master-standardize-npm
Jun 3, 2026
Merged

chore: standardize on npm, remove yarn.lock (re-target to master)#222
sameh-farouk merged 2 commits into
masterfrom
master-standardize-npm

Conversation

@sameh-farouk

Copy link
Copy Markdown
Member

Re-merge of #221 to master. #221 was merged into its stacked base master-update-compose-stacks instead of master (base wasn't retargeted). This PR brings the identical npm-standardization changes onto master: removes yarn.lock, adds package-lock.json consistency, converts CI/docker-compose/scripts/docs from yarn to npm.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

sameh-farouk and others added 2 commits April 6, 2026 16:39
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 sameh-farouk merged commit 62ed815 into master Jun 3, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant