Closed KnorpelSenf closed 9 months ago
There is already https://github.com/denoland/node_shims which provides all the Deno APIs in Node.
Could you explain why you decided against integrating the npm package @deno/kv into the existing project? It would be a natural fit, no?
@deno/kv
Do you have plans to add it there as a re-export?
https://github.com/denoland/denokv repo is dedicated to projects related to Deno KV, which makes it a natural fit for KV npm package. There are no plans to move it to https://github.com/denoland/node_shims.
There is already https://github.com/denoland/node_shims which provides all the Deno APIs in Node.
Could you explain why you decided against integrating the npm package
@deno/kv
into the existing project? It would be a natural fit, no?Do you have plans to add it there as a re-export?