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

Bun · all subjects

package manager & installation

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.

Install Hono project dependencies

After creating a Hono project with Bun, run 'bun install' to ensure all project dependencies are installed.

Bun package manager commands - install packages

Install a package with `bun add <package>`. Install as a dev dependency with `bun add -D <package>`.

Install dependencies with Bun in a Vite project

After creating a Vite project, install dependencies using 'bun install' in the project directory.

Bun downloads GitHub dependencies as HTTP tarballs when possible

Bun optimizes downloading GitHub dependencies by using HTTP tarballs when possible, which is faster than other methods.

Optional dependencies in package.json

When a package is added with the `--optional` flag, it is listed in the `optionalDependencies` field of `package.json` rather than `dependencies` or `devDependencies`.

Configure Azure Artifacts registry with bunfig.toml

To configure Azure Artifacts as an npm registry with Bun, create a bunfig.toml file with [install.registry] section containing: url set to the Azure Artifacts npm registry URL (format: https://pkgs.dev.azure.com/my-azure-devops-org/_packaging/my-feed/npm/registry/ for organization-scoped feeds, or https://pkgs.dev.azure.com/my-azure-devops-org/my-project/_packaging/my-feed/npm/registry/ for project-scoped feeds), username set to any non-empty string, and password which can be an environment variable reference like $NPM_PASSWORD. Do not base64 encode the password in bunfig.toml; Bun will do that automatically.

Configure Azure Artifacts with NPM_CONFIG_REGISTRY environment variable

To configure Azure Artifacts without bunfig.toml, set the NPM_CONFIG_REGISTRY environment variable with the format: https://pkgs.dev.azure.com/my-azure-devops-org/_packaging/my-feed/npm/registry/:username=<USERNAME>:_password=<PASSWORD>. Append the credentials directly to the URL separated by colons. Do not base64 encode the password when using NPM_CONFIG_REGISTRY.

Password encoding in bunfig.toml vs .npmrc files

When using bunfig.toml or NPM_CONFIG_REGISTRY, provide passwords in plain text and do not base64 encode them; Bun will base64 encode the password automatically. However, when using .npmrc files directly, the _password field must remain base64 encoded, as per Azure's standard instructions. This difference applies specifically when using different configuration methods with Bun.

Azure DevOps personal access token characteristics

Azure DevOps personal access tokens are 84 characters long. When base64 encoded, they become 112 characters long and do not end with an equals sign (=).

Give your agent this brain