Skip to content

suggestion: @std/kv #6387

Open
Open
@iuioiua

Description

I suggest moving @deno/kv-utils to @std/kv. While these utilities have fairly niche use cases, creating @std/kv can offer some possible benefits:

  1. These utilities would have far greater visibility in the Deno Standard Library. I only just discovered @deno/kv-utils and it's been around for a few months.
  2. Can increase awareness of Deno KV.
  3. Increases the chances that devs imagine up and create better tools for Deno KV.
  4. Possibly serve as a test bench for ideas that could be implemented in the runtime. E.g. a JavaScript/TypeScript version of Deno.Kv.count() until it's implemented in the runtime.

Related #6123

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions