Docs / quickstart

Production

Two ways to ship packages.

Use the npm-compatible gateway for public packages, or the native registry for packages you publish through Lemonize.

01 / npm edge gateway

Install through the CDN

Gateway status

Add the registry flag to one install. npm still resolves the public package; Lemonize provides the metadata and tarball route through Cloudflare.

npm install zod --registry=https://npm.lemonize.cyou

Edge hits stay close

Cacheable responses are reused from Cloudflare's network after the first fetch.

No package archive

Public npm tarballs are streamed and cached, not copied into Lemonize R2 storage.

npm install -g @lemonize/cli --registry=https://npm.lemonize.cyou

Make it the project default

Save the registry in your project-level .npmrc. Commit that choice only if every contributor should use the gateway.

npm config set registry https://npm.lemonize.cyou --location=project

02 / native registry

Prepare a native package

The workflow below applies after the write gate is enabled. Production is currently read-only: existing packages remain installable, while new package and version writes are rejected.

  1. 1

    Install the CLI

    npm install -g @lemonize/cli
  2. 2

    Authenticate

    lem login
    lem config set registry https://registry.lemonize.cyou
  3. 3

    Publish

    lem init && lem publish
  4. 4

    Install and run

    lem add @demo/utils --source lemonize
    lemx create-lemon-app -- --template minimal

03 / delivery model

Know what is stored

Public npm packages

Requested from npm on demand and cached by Cloudflare when eligible. They are not archived in Lemonize's R2 bucket.

Native Lemonize packages

Stored immutably in R2 and served through the registry download gateway. The CLI verifies SHA-512 before extraction.

Need an account? Sign in with GitHub.