github / github/paste-markdown

Update devcontainer with chromium dependencies

Offen
#52 0 Kommentare 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
JavaScript
Sterne
234
Forks
47
Ø Merge
1 T. 12 Std.
Gemergte PRs (30 T.)
5

Beschreibung

When attempting to `npm install && npm run test` in a fresh codespace, we initially see an error related to a missing shared library:
```
26 04 2022 14:32:23.081:ERROR [launcher]: Cannot start ChromeHeadless
/workspaces/paste-markdown/node_modules/chromium/lib/chromium/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
```

Running
```
ldd /workspaces/paste-markdown/node_modules/chromium/lib/chromium/chrome-linux/chrome | grep not
```
shows a list of libraries similar to that in https://github.com/dtolstyi/node-chromium/issues/52#issuecomment-1028727251

```
libnss3.so => not found
libnssutil3.so => not found
libsmime3.so => not found
libnspr4.so => not found
libatk-1.0.so.0 => not found
libatk-bridge-2.0.so.0 => not found
libcups.so.2 => not found
libdrm.so.2 => not found
libxkbcommon.so.0 => not found
libXcomposite.so.1 => not found
libXdamage.so.1 => not found
libXfixes.so.3 => not found
libXrandr.so.2 => not found
libgbm.so.1 => not found
libpango-1.0.so.0 => not found
libcairo.so.2 => not found
libasound.so.2 => not found
libatspi.so.0 => not found
```
^^ This correlates pretty well to https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#chrome-headless-doesnt-launch-on-unix

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Inspect the repository's devcontainer configuration and reproduce the failure with `npm install && npm run test` in a fresh Codespace. Use `ldd` on the Chromium binary to verify the missing libraries listed in the issue. Done means ChromeHeadless starts successfully and the test command no longer reports missing shared libraries.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
javascript, node.js
Bereich
devops, testing-qa
Issue-Typ
Bug
Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
45/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.