Marek Krajčovič

I'm having the same problem with export asynchronicity. I check for exporting `store.json` before resolving the promise, which seems to always be the last key to go, but it's pretty...

I'm seeing the same problem with mocha. nyc reports 0 coverage for native esm. (node 12 with `--experimental-modules --experimental-json-modules` flags)

Not the maintainer, but `decodeEntities` controls the opposite - if `>` in the input should become `>` in the output. I think you want `xmlMode: true` instead.

You can point the TS_NODE_PROJECT variable in your vscode settings to a "modern" tsconfig ``` "code-runner.executorMap": { "typescript": "TS_NODE_PROJECT=~/stuff/tsconfig.json ts-node" } ```

I've had a similar issue with `wine` not working in our kubernetes/jenkins environment, but `wine64` working fine. I had no control on what electron-builder uses though, so I symlinked wine...

I believe this is related https://github.com/cheeriojs/cheerio/issues/2841 and really unfortunate 😬 That regex can get heavy for huge htmls