Binding reference Bindings

Use Artifacts in a Worker

Artifacts bindings let Workers create and manage Git-compatible repos and repo tokens.

Add the Artifacts config, call from worker code, and start with the local test path Devflare supports.

Start with the config, wire the binding into worker code, then use the support section to decide whether local tests or Cloudflare-backed tests fit.

Config key
Authoring shape
Best for: Worker-managed repo metadata, temporary tokens, and artifact namespace workflows

Add the binding to config

Add to , then use the generated env binding from Worker code.

Keep the first version close to the route or handler that needs it; move to a helper only after the shape is obvious.

Smallest Artifacts config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'artifact-worker',

bindings: {

artifacts: {

ARTIFACTS: 'build-artifacts'

}

})

Use the binding from application code

After Devflare generates the worker env, import from and keep the first Artifacts path close to the route, handler, or service method that needs it.

Keep this first path small enough that the config, env binding, and user-visible behavior are easy to review together.

Create one Artifacts repository

import { env } from 'devflare/runtime'

export async function fetch(): Promise<Response> {

const repo = await env.ARTIFACTS.create('run-logs', {

description: 'CI run logs'

})

return Response.json({ remote: repo.remote })

}

Local and Remote Support

Devflare supports the config, generated env shape, docs, and local application-flow work, but full fidelity requires Cloudflare remote infrastructure. Use local shims or fixtures for code your app owns, then connect to Cloudflare when the product behavior is the assertion.

Offline-fixture: repo metadata and token flows can be modeled in memory, not as real Git remotes. Keep local coverage focused on deterministic application flow through fixtures, mocks, shims, or Miniflare-backed wiring instead of pretending to reproduce Cloudflare-hosted product behavior.

Use Cloudflare when the assertion depends on cloudflare-hosted product behavior rather than the app calling the binding correctly. This is the lane for full Artifacts product fidelity, remote state, lifecycle behavior, and platform-specific limits.

When this binding fits best

Use Artifacts when worker-managed repo metadata, temporary tokens, and artifact namespace workflows.
Keep binding names stable and uppercase in examples so generated Env declarations remain predictable.
Prefer Devflare native config while it covers the feature; use only for unsupported Wrangler-only fields.

Testing path

Start with with artifact fixtures for config-backed local worker tests.
Use / for small unit tests that only need deterministic application behavior.
Use Cloudflare-backed tests when the assertion depends on hosted platform behavior, account state, limits, billing, or production routing.

Open the next page when you need it

Subpage

Artifacts internals

Internals

Check emitted Wrangler , preview behavior, and Cloudflare-specific details.

Subpage

Testing Artifacts

Testing

Pick the with artifact fixtures path first, then move to remote checks only when the test needs them.

Subpage

Artifacts example

Example

Copy a fuller application path when the quick example is too small.