Ger Hobbelt

The quick & dirty way was to simply nuke grunt-readme and grunt-templates-dylang (which depends on readme). ... ah well...

You're calling .render() on each event and one of them has .invalidateRows() (as it should), so yes, this is expected behaviour. ## Advanced / Suggestion how to fix/optimize this out...

1. 💯 on the zstd compression level, i.e. zstd / lz4 compression configurable from the CLI. 🥳 2. re *other compressors* & *other image formats*: depends, can get pretty wild....

# Post Scriptum After re-installing nvm-windows (WITHOUT uninstalling it first!), the `nvm use x.y.z` commands do deliver as expected. No more error dialog from elevate.vbs and no need to go...

Yes, I have tried to invoke nvm from git-bash, and hit the issue then. *however*, I also tried running it from a `cmd` shell which itself was started from a...

I may be wrong here re zmq specifics, but generally when handles have a lifetime intersected by a `fork()` then *both* parent *and* client need to close the handle. i.e....

Same problem here. This time, `SUBST`-based. See https://github.com/istanbuljs/test-exclude/issues/46#issuecomment-873377302

The (TEMPORARY) fix in my own codebase uses run-time detection of istanbul, i.e. a function which checks if my code is executing in an istanbul/nyc environment. Now the tests PASS...

``` $ node --version v12.18.4 ``` No, haven't tried other versions, but have seen this issue before. Then I switched tactics as I was in a hurry to get things...

Side Note: globby use like this (i.e. without **directories** in the search argument) works as expected: ```js globby([ 'ebnf-parser*.js' ]) ```