Alec Larson

I forked this repo and updated it to use [**jasmine-core**](https://www.npmjs.com/package/jasmine-core) instead of embedding Jasmine as part of this package. So you should (in theory) be able to use any version...

@abritinthebay Correct. I'll update the README to reflect that. Luckily there's no reason to use my fork if you use any version of Jasmine

This isn't a problem in [filespy](https://github.com/alloc/filespy), an alternative to chokidar.

Can someone confirm if this problem is fixed by [filespy](https://github.com/alloc/filespy)?

This isn't a problem in [filespy](https://github.com/alloc/filespy), an alternative to chokidar.

This works as expected in [filespy](https://github.com/alloc/filespy), an alternative to chokidar.

I'm facing the same error. Using the `--debug` flag, it seems that [the request](https://bundlesize-store.now.sh/build?info=%7B%22files%22%3A%5B%7B%22maxSize%22%3Anull%2C%22path%22%3A%22dist%2Findex.js%22%2C%22size%22%3A4877%2C%22compression%22%3A%22gzip%22%7D%5D%7D) to `bundlesize-store.now.sh` is hitting an internal server error. ```sh $ GITHUB_REPOSITORY="alloc/wana" GITHUB_SHA="master" BUNDLESIZE_GITHUB_TOKEN="[redacted]" ./node_modules/.bin/bundlesize -f "dist/index.js"...

Strangely, the readme for `libmdbx` lists this as a feature: > Nested write transactions. ..yet the error message implies write transactions cannot be nested.

The docs for `libmdbx` say otherwise (emphasis mine): > A transaction and its cursors must only be used by a single thread, and **a thread may only have a single...

Ah, the devil is in the details. The `parent` argument to `mdbx_txn_begin` is what "nested write transactions" refers to. In other words, the nesting must be explicit. > If this...