You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had done the workaround in my main branch and thought it was about working but I notice the the error come back if I run pnpm i --lockfile-only:
➜ raulmelo-studio git:(main) ✗ pnpm i
Scope: all 8 workspace projects
Lockfile is up-to-date, resolution step is skipped
Already up-to-date
apps/fitness-buddy postinstall$ pnpm run typegen
│ > fitness-buddy@0.0.1 typegen /Users/raulmelo/development/raulmelo-studio/apps/fitness-buddy
│ > xstate typegen "src/**/*.ts?(x)"
│ src/lib/stores/trainingMachine.ts - success
└─ Done in 713ms
apps/fitness-buddy prepare$ svelte-kit sync
└─ Done in 191ms
➜ raulmelo-studio git:(main) ✗ pnpm i --lockfile-only
Scope: all 8 workspace projects
WARN `node_modules` is present. Lockfile only installation will make it out-of-date
ERROR Cannot convert undefined or null to object
Progress: resolved 0, reused 1, downloaded 0, added 0
pnpm version: 7.1.5
Code to reproduce the issue:
pnpm.debug.log
: https://mega.nz/file/It11VQ6Y#bgxRFLnQqqclN8npto-VUosfrHK3TC6Q-YMvmhcqzAE (couldn't paste here due Github limitationComment is too long (maximum is 65536 characters)
)cannot-convert-undefined-or-null-to-object
pnpm i
Cannot convert undefined or null to object
You can also try remove
pnpm.lock.yaml
and runpnpm i
again. The error will still remain.I think this is, somehow, related to
auto-install-peers=true
present in the.npmrc
because if I:auto-install-peers
tofalse
;pnpm i
(it'll run successfuly) and throw errors due missing peerDeps;auto-install-peers
totrue
;pnpm i --force
(no missing peerDeps error)I won't get
Cannot convert undefined or null to object
.Expected behavior:
Either install deps and regen lock file or give me a good error message so I have a clue what's wrong and fix the issue.
Actual behavior:
Blocks the installation.
Additional information:
node -v
prints: v16.14.2The text was updated successfully, but these errors were encountered: