Deno init with npm flag creates Vite project
Running 'deno init --npm vite' initializes a new Vite project and prompts you to give your project a name and select your framework and variant.
cli commands & arguments
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 doc basic terminal output
Run 'deno doc math.ts' to output documentation to the terminal. This shows all exported functions, classes, and interfaces with their JSDoc comments.
deno doc --html flag generates static website
Use 'deno doc --html --name="Math Utilities" math.ts' to generate a static documentation website in the ./docs/ directory. The site includes a searchable interface, syntax highlighting, cross-references between symbols, and mobile-friendly responsive design.
deno doc --output custom directory
Use the --output flag to specify a custom output directory for HTML documentation: 'deno doc --html --name="Math Utilities" --output=./documentation/ math.ts'
deno doc --lint checks for documentation issues
Run 'deno doc --lint math.ts' to check for documentation issues. The linter reports three categories of problems with named error codes: 'missing-jsdoc' (an exported symbol has no JSDoc comment), 'missing-return-type' (an exported function has no explicit return type annotation), and 'private-type-ref' (a public export references a type that is not itself exported, so consumers can't name it).
deno doc --json generates JSON format
Run 'deno doc --json math.ts > documentation.json' to generate documentation in JSON format for use with other tools. The JSON output provides a low-level representation of code structure, including symbol definitions and basic type information, useful for building custom documentation tools or integrating with other systems.
deno doc works with multiple files
You can document multiple files at once with 'deno doc --html --name="My Library" ./mod.ts ./utils.ts ./types.ts'.
deno ci command
deno ci installs dependencies from the lockfile. It mirrors npm ci: it is roughly equivalent to deleting node_modules and running deno install --frozen. It errors out if deno.lock is missing, and fails if deno.json or package.json changed without the lockfile being refreshed.
deno ci requires committed deno.lock
deno ci requires a committed deno.lock file. If your repository doesn't have one yet, run deno install locally and commit the resulting lockfile.