Tiny Engine License

Package URL: https://www.npmjs.com/package/tiny-engine-license

What it is

tiny-engine-license is separate from tiny-engine-core. Keep the core runtime small and dependency-light, then add the license package only in projects that need license-aware distribution or access checks.

From a package manager

Pick your favourite - they're all equivalent.

License key setup

Keep license keys outside source control, then read them from your deployment environment or local .env file.

TINY_ENGINE_LICENSE_KEY=your_license_key_here

# CI / hosting environment
TINY_ENGINE_LICENSE_KEY=prod_xxxxxxxxxxxxx
TINY_ENGINE_LICENSE_OWNER=your-team-or-company
TINY_ENGINE_LICENSE_PACKAGE=tiny-engine-license

Recommended flow

1. Store the license key in CI or server-only environment config.
2. Verify the key before build, publish, or premium feature startup.
3. Keep browser bundles free of private production keys.
4. Fail closed when a private add-on cannot verify its license.

{
  "scripts": {
    "prebuild": "your-license-check-command",
    "build": "next build"
  }
}

Replace your-license-check-command with the command or script your project uses to call the license package.

When to use it

• Protecting private Tiny Engine packages or premium capsules.
• Checking license status before enabling add-on features.
• Keeping license validation separate from UI runtime code.
• Running license checks in CI before publishing internal builds.

Where it fits

tiny-engine-core stays focused on runtime behavior.tiny-engine-license is the companion layer for projects that need license-aware distribution or package access checks.

1.8.0 package set

Tiny Engine 1.8.0 documents the core runtime and the first companion package together. Use tiny-engine-core for capsules, lifecycle, store, devtools, and plugins. Use tiny-engine-license when a project also needs license-key handling around private or paid package features.