den.ooo

den.ooo

Setup

Deno

deno.json

{
  "den.ooo": "https://esm.sh/den.ooo@1.2.0"
}

Node.js

npm i den.ooo

Usage

import { Registry } from 'den.ooo'
import { GitHub, GitLab, NPM } from 'den.ooo/resolvers'

const registry = new Registry({
  resolvers: [
    GitHub,
    GitLab,
    NPM
  ],
  ... // see below for more detailed customization
})

// Deno
await registry.serve()

// Cloudflare Workers
export default registry

• domain string - The domain of your server, e.g. den.ooo.

• versionCache - Provide simple set and get functions that the proxy can use to cache versions of modules to reduce requests to third-party APIs. Where the data is stored is up to you.

• fileCache - Provide simple set and get functions that the proxy can use to cache JavaScript, TypeScript and WebAssembly files. Where and for how long the data is stored is up to you.

• features

  • aliases Record<string, string> (default: {})
  • typesHeader boolean (default: false)
  • importMapResolution boolean (default: false)
  • enforceSemVer boolean (default: true)

Stability

All features of den.ooo have been repeatedly tested. Should you nevertheless encounter an unexpected problem, please make sure to open a new issue to draw our attention to the bug so that we can fix it as quickly as possible.

Want to deploy your own registry?

If you're interested in deploying your own version of den.ooo, feel free to take inspiration from the below examples, or if you don't want to waste too much time, use our starter template for Railway instead.

• ☁️ Cloudflare Workers

  • Module Aliases
  • Redis Version Cache (over HTTP)

• 🦕 Deno

  • Module Aliases
  • Redis Version Cache (over TCP)