ende publish

ende publish publishes your package to the JSR registry.

Package Requirements

Your package must have a name and version and an exports field in its ende.json or jsr.json file.

• The name field must be unique and follow the @<scope_name>/<package_name> convention.
• The version field must be a valid semver version. To bump it as part of your release flow, see ende bump-version.
• The exports field must point to the main entry point of the package. The exports field can either be specified as a single string, or as an object mapping entrypoint names to paths in your package.

Example:

{
  "name": "@scope_name/package_name",
  "version": "1.0.0",
  "exports": "./main.ts"
}

Before you publish your package, you must create it in the registry by visiting JSR - Publish a package.

Excluding a workspace member

When run inside a workspace, ende publish tries to publish every member that has a name and exports, and errors if any of them is missing a version. To opt a member out, for example an internal helper package that only exists to host shared tasks, set "publish": false in that member's ende.json:

{
  "name": "@scope/internal-helpers",
  "publish": false
}

The member stays part of the workspace but is skipped by ende publish. See Excluding a workspace member from publish for the full discussion.

Examples

Publish your current workspace

ende publish

Publish your current workspace with a specific token, bypassing interactive authentication

ende publish --token c00921b1-0d4f-4d18-b8c8-ac98227f9275

Publish and check for errors in remote modules

ende publish --check=all

Perform a dry run to simulate publishing.

ende publish --dry-run

Publish using settings from a specific configuration file

ende publish --config custom-config.json

publish