new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Deno · Reference · all subjects

configuration/deno.json

11 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.json preferPackageJson configuration

Setting "preferPackageJson": true in deno.json makes --package-json the default behavior for deno add without needing to pass the flag each time.

deno check exclude field in deno.json

Use the top-level exclude field in deno.json to skip files or directories when running deno check. The exclude field applies to deno check along with other subcommands like deno fmt and deno lint. Example: {"exclude": ["dist/", "vendor/", "**/*.generated.ts"]}

deno compile include and exclude in deno.json

The --include and --exclude paths can be set declaratively in deno.json under the 'compile' section, so you don't have to repeat them on every deno compile invocation. CLI flags are merged with the config: --include and --exclude add to the lists in deno.json rather than replacing them.

deno compile include/exclude deno.json example

Example deno.json configuration: { "compile": { "include": ["names.csv", "data", "worker.ts"], "exclude": ["data/secrets", "**/*.test.ts"] } }

deno.json desktop configuration block

Most settings can be configured in the desktop block of deno.json instead of being passed on every build. The desktop block can contain: app (with name, identifier, and icons), backend, output, release, and errorReporting fields.

deno.json desktop configuration example

Example deno.json desktop configuration: { "desktop": { "app": { "name": "MyApp", "identifier": "com.example.myapp", "icons": { "macos": "./icons/icon.icns", "windows": "./icons/icon.ico", "linux": "./icons/icon.png" } }, "backend": "cef", "output": { "macos": "./dist/macos", "windows": "./dist/windows", "linux": "./dist/linux" }, "release": { "baseUrl": "https://updates.example.com" }, "errorReporting": { "url": "https://errors.example.com/report" } } }

deno.json fmt configuration options

The fmt block in deno.json supports the following configuration options: useTabs (boolean), lineWidth (number), indentWidth (number), semiColons (boolean), singleQuote (boolean), and proseWrap (string). Example: {"fmt": {"useTabs": false, "lineWidth": 80, "indentWidth": 2, "semiColons": true, "singleQuote": false, "proseWrap": "preserve"}}.

deno.json fmt include and exclude options

The fmt block in deno.json supports include and exclude options to specify which files to format. Example: {"fmt": {"include": ["src/"], "exclude": ["src/testdata/", "src/generated/**/*.ts"]}}.

deno.json lint rules configuration

In deno.json, configure linting rules under the 'lint' object with 'rules' containing: tags (array of rule sets like 'recommended' or 'fresh'), include (array of individual rule names to enable), and exclude (array of rule names to disable).

deno.json lint file inclusion/exclusion

In deno.json, specify files to lint using the 'lint' object with 'include' (array of directories/files to lint) and 'exclude' (array of patterns to exclude, supporting glob patterns like 'src/generated/**/*.ts').

Configure unstable flags in deno.json

Unstable features can be configured in deno.json using the 'unstable' array, with flag names having the '--unstable-' prefix removed. Example: { "unstable": ["sloppy-imports", "webgpu"] }

Give your agent this brain