Oskari Noppa

We also started facing this today. Puppeteer crashes, and the Chromium logs contain ``` [ERROR:nss_util.cc(124)] Error initializing NSS without a persistent database: NSS error code: -8023 ``` The breakage seems...

Rebuilding the layer with the latest version (123.0.1) of `@sparticuz/chromium` fixed the issue for us. We were using version 117 before. Plus we had to re-enable `setGraphicsMode` due to #247,...

I could take a look, but I'd need to be able to reproduce the error first. Can you post the output of ```sh npm version ``` Are you running on...

Thanks, I don't have a Mac available but I'll try to reproduce with the other environment specs

Thanks for the test XML, I was able to reproduce the issue. I have a possible (not yet very well tested) fix, here: [v5.0.0-alpha](github.com/noppa/xmllint-wasm/releases/tag/v5.0.0-alpha) (PR #21). Could you test with...

Sweet. I'm a bit busy for a few days but will try to test and craft a proper release soonish. Meanwhile, the github alpha release should work fine.

This is also now in npm, with version [5.0.0-rc.0](https://www.npmjs.com/package/xmllint-wasm/v/5.0.0-rc.0). I'll also test this in prod a bit before I dare to tag that as the latest release.

What kind of bundler/build setup are you using? The stack trace implies that there may be some stuff going on that isn't coming from this lib, but probably zone.js. Sooo......

The only way that I can think of that this could happen is that if this line [in index.js](https://github.com/noppa/xmllint-wasm/blob/master/src/index.js#L162C20-L163C94) throws ```javascript worker = new Worker(new URL('./xmllint-browser.mjs', import.meta.url), { type: 'module'...

I have fixed the confusing `Cannot read properties of undefined` error on version 4.0.2. This won't fix your actual issue, because for some reason or another the code running in...