Wire frontend/react-native-expo for pnpm 11 (config only; lockfile follow-up)#48
Draft
Gabrielpanga wants to merge 1 commit into
Draft
Wire frontend/react-native-expo for pnpm 11 (config only; lockfile follow-up)#48Gabrielpanga wants to merge 1 commit into
Gabrielpanga wants to merge 1 commit into
Conversation
…llow-up)
Config-only bump. The pnpm-lock.yaml and removal of the old
package-lock.json / .npmrc need to happen on a machine that can run
`pnpm install` — this PR intentionally stops short of that step.
package.json
- packageManager: pnpm@11.1.1
- engines: node >=24.0.0, pnpm >=11.0.0
- devEngines.runtime with onFail: error
- scripts.preinstall: pnpm audit && pnpm audit signatures
- scripts.lint:lockfile: pnpm install --frozen-lockfile
- scripts.typecheck: tsc --noEmit
- scripts.lint: tsc --noEmit (was `expo lint`; expo lint is
ESLint-config-aware but errors out interactively if config isn't
present — typecheck is the safe baseline until a real eslint setup
is added)
- scripts.test / scripts.build: tsc --noEmit
pnpm-workspace.yaml — full supply-chain stack:
- minimumReleaseAge: 20160 (14d)
- minimumReleaseAgeIgnoreMissingTime: true
- minimumReleaseAgeExclude: '@pluggyai/*'
- engineStrict: true
- trustPolicy: no-downgrade, trustPolicyIgnoreAfter 90d
- blockExoticSubdeps: true
- savePrefix: ""
- resolutionMode: highest
- allowBuilds: {} (to be populated on first `pnpm install` — Expo
ships native deps like reanimated that have postinstall scripts)
- overrides: {}
.gitignore — block package-lock.json and yarn.lock
Follow-up (separate PR):
1. Run `pnpm install` to generate pnpm-lock.yaml.
2. Delete .npmrc and package-lock.json (the install above already
leaves both stale).
3. Populate pnpm-workspace.yaml allowBuilds with conscious yes/no
decisions for each native dep that asks for a postinstall.
4. Re-run audit / fix any vulns surfaced.
5. Add .github/workflows/expo-ci.yml matching the other per-project
workflows.
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.
Summary
Draft. Config-only bump for `frontend/react-native-expo`. This PR sets up the pnpm 11 metadata + supply-chain hardening but does not run `pnpm install` — the `pnpm-lock.yaml` and the removal of the old `package-lock.json` / `.npmrc` need to happen on a machine that can actually install (Expo pulls native deps that may need their own postinstall decisions).
What's in this PR
`package.json`
`pnpm-workspace.yaml` — full supply-chain stack:
`.gitignore` — adds `package-lock.json` and `yarn.lock`.
Follow-up required before merging