failed to parse .../pnpm-lock.yaml: invalid type: string "glibc" #336
-
|
I recently discovered aube (via mise) and was quite exited about it as it claims this amazing speed and that it can be used as a drop-in replacement of from our pnpm-lock.yaml Is this a bug? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Yes, this was a bug in aube’s pnpm lockfile parser. pnpm can emit package platform fields like I opened a fix here: #337 Thanks for the clear report and lockfile snippet. Discussions are the right place for this repo; Issues are disabled to keep project maintenance sustainable. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also seeing this with invalid type: string "glibc", expected a sequence at line 66019 column 27
"node_modules/sass-embedded-linux-arm": {
"version": "1.99.0",
"resolved": "https://registry.npmjs.org/sass-embedded-linux-arm/-/sass-embedded-linux-arm-1.99.0.tgz",
"integrity": "sha512-d4IjJZrX2+AwB2YCy1JySwdptJECNP/WfAQLUl8txI3ka8/d3TUI155GtelnoZUkio211PwIeFvvAeZ9RXPQnw==",
"cpu": [
"arm"
],
"dev": true,
"libc": "glibc",
"license": "MIT",
"optional": true,
"os": [
"linux"
],
"engines": {
"node": ">=14.0.0"
}
}, |
Beta Was this translation helpful? Give feedback.
-
|
@joshkaplinsky thanks for the follow-up — confirmed the npm parser had the same gap as the pnpm one. Same root cause: Fix in flight: #405. Reuses the existing Written with Claude. |
Beta Was this translation helpful? Give feedback.
-
|
wow! bug fix in less than 30 minutes, that's really amazing! 🎉 🙇 when will the next version be released that contains this fix? |
Beta Was this translation helpful? Give feedback.
Yes, this was a bug in aube’s pnpm lockfile parser.
pnpm can emit package platform fields like
os,cpu, andlibceither as arrays or as scalar strings. Aube already handled that shape for registry packuments, but the pnpm lockfile parser was only accepting arrays, solibc: glibcfailed to deserialize.I opened a fix here: #337
Thanks for the clear report and lockfile snippet. Discussions are the right place for this repo; Issues are disabled to keep project maintenance sustainable.