logseq / logseq/logseq-plugin-samples
Node 22 broken for ARM macOS
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- CSS
- Sterne
- 383
- Forks
- 97
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
I've been testing a variety of sample plugins, and they all seem broken during build. i came across a reference to the error that was happening during the build, and it suggested that the issue has something to do with an incompabitiblity between node 22 and something in @libseq/libs that is not in node 20. I used nvm to switch to node 20, and each sample repo built successfully.
Node 22:
ogseq-plugin-samples/logseq-a-translator on master [!?] is 📦 v0.0.1 via v22.9.0 via 💎 v3.0.5 took 3s
❯ npm run build
> logseq-a-translator@0.0.1 build
> parcel build --public-url . --no-source-maps index.html
(node:95127) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
⠙ Building index.html...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly: https://github.com/browserslist/browserslist#brows
⠸ Building index.ts...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly: https://github.com/browserslist/browserslist#brows
⠼ Building index.ts...
node(95127,0x16fd9b000) malloc: Incorrect checksum for freed object 0x11d8c0e00: probably modified after being freed.
Corrupt value: 0x10220a4930383839
node(95127,0x178407000) malloc: Incorrect checksum for freed object 0x10a847600: probably modified after being freed.
Corrupt value: 0x10220a4930383839
node(95127,0x178407000) malloc: *** set a breakpoint in malloc_error_break to debug
node(95127,0x16fd9b000) malloc: *** set a breakpoint in malloc_error_break to debug
zsh: abort npm run build
Node 20:
logseq-plugin-samples/logseq-a-translator on master [!?] is 📦 v0.0.1 via v20.18.0 via 💎 v3.0.5 took 3s
❯ npm run build
> logseq-a-translator@0.0.1 build
> parcel build --public-url . --no-source-maps index.html
⠙ Building index.html...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly: https://github.com/browserslist/browserslist#brows
⠹ Building index.html...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly: https://github.com/browserslist/browserslist#brows
⠼ Building lsplugin.user.js...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
Why you should do it regularly: https://github.com/browserslist/browserslist#brows
✨ Built in 1.09s
dist/index.html 383 B 471ms
dist/index.9947b3c0.js 90.11 KB 213ms
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne damit, npm run build in einem Beispiel-Plugin mit Node 22 und Node 20 zu reproduzieren, wobei der Build von index.ts und die gemeldete Inkompatibilität von @libseq/libs im Mittelpunkt stehen. Vergleiche die von den Beispiel-Repositories verwendeten Abhängigkeiten und Build-Konfigurationen; abgeschlossen ist die Aufgabe, wenn sich die Beispiele auf ARM macOS mit Node 22 erfolgreich bauen lassen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- nodejs
- Bereich
- build-system
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100