deno.json example for publish
Example deno.json for publishing: {"name": "@scope_name/package_name", "version": "1.0.0", "exports": "./main.ts"}
Deno · Reference · all subjects
cli commands/publish
9 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
deno publish basic example
To publish your current workspace, run: deno publish
deno.json package requirements for publish
To publish a package, the deno.json or jsr.json file must contain three required fields: name, version, and exports. The name field must follow the @<scope_name>/<package_name> convention and be unique. The version field must be a valid semver version. The exports field must point to the main entry point of the package and can be either a single string or an object mapping entrypoint names to paths.
deno publish --token flag
The --token flag accepts a JSR registry token to bypass interactive authentication. Example: deno publish --token c00921b1-0d4f-4d18-b8c8-ac98227f9275
deno publish --check flag
The --check flag accepts a value to control error checking. The value 'all' checks for errors in remote modules. Example: deno publish --check=all
deno publish --dry-run flag
The --dry-run flag performs a dry run to simulate publishing without actually publishing the package.
deno publish --config flag
The --config flag specifies a custom configuration file to use for publish settings. Example: deno publish --config custom-config.json
Excluding workspace members from publish
When running deno publish inside a workspace, it attempts to publish every member that has a name and exports field. To opt out a workspace member from publishing, set 'publish': false in that member's deno.json file. The member remains part of the workspace but is skipped during publish.
deno.json publish field for workspace members
Example of excluding a workspace member from publish in internal-helpers/deno.json: {"name": "@scope/internal-helpers", "publish": false}