Tess Rosania

We've been tracing an issue where `npm` seems to sporadically rewrite our `package-lock.json`. It seems to only happen to dependencies of Electronegativity. I suspect it's related to the use of...

This has started causing a new problem for us as well, since `npm-shrinkwrap.json` includes things like `fsevents` v1.2.12, which causes install to fail on Windows. `fsevents` is a dependency of...

@ikkisoft this bit from that Yarn blog post is the key: >When you install dependencies in your application or library, only your own yarn.lock file is respected. As @balgillo mentions,...

Understood! Have you considered separating out the library from the CLI and publishing them as separate artifacts? That might solve the problem of publishing `npm-shrinkwrap.json` while letting people consume the...

@JoshuaWise would you be open to a PR that ported the V8 interface to N-API? I've been noodling on the continuous maintenance needed for Electron (#638, #693, etc.) and I...

Bumping this. I'm interested in taking this on, although I believe it's worthwhile porting off `lzz` onto vanilla C++ as part of this change. `lzz` is a learning barrier to...

Incredible, thank you!

This would be incredibly helpful for us, and would let us use Prisma in a large chunk of our codebase. We currently rely on in-memory Sqlite for all of our...

I believe I've isolated a spot where support could be added relatively easily: https://github.com/prisma/quaint/blob/d897d94617f37bede2f9e53d56d4a6df7c3a0e00/src/pooled/manager.rs#L88 If I understand correctly, a URL string convention similar to `:memory:` could be used to invoke...

I think it could be quite surgical -- if I understand the linked code correctly, it would be as simple as invoking the database using `new_in_memory` instead of `new` in...