Matteo Collina

CI is failing

Apparently vite-plugin-node requires vite v4.0.0: https://github.com/axe-me/vite-plugin-node/blob/b9ff47f6f02b4ffd4648812a3de6d5d133879ac6/packages/vite-plugin-node/package.json#L41 I think you can set legacy-peeer-deps in the `.npmrc`: https://github.com/npm/rfcs/discussions/283

Might it be possible that you are running multiple servers connecting to the same SQLite instance? See https://www2.sqlite.org/cvstrac/wiki?p=DatabaseIsLocked for examples.

> Isn't the idea that the sql cache should work cross process? We should probably handle errors like these? Yes! 100%. However I'm not really sure how to handle this...

> I thought sqlite was designed not to have this issue? Unfortunately no, you can have this issue in SQLite as the link above describe. However, this shouldn't really be...

There can be an overlap between write and reads _only_ if two happen in parallel, but this shouldn't be possible because the SQLite docs clearly states that the locked status...

We haven't really assessed if/how this would integrate with fetch.

@walkerburgin can you assemble an reproduction of this problem? Because I'm not seeing it in my codebase: pnpm creates a directory structure that resolves this correctly.

Unfortunately `peerDependencies` cause more problems that they are worth (especially with such a wild range of versions of npm, yarn, pnpm etc). We tend to follow the "standard behavior" of...

I think a PR with the change would help us spot why we did not pass it. If it's that's the case there is likely a test to cover it.