Bascik Configuration and Deployment

Bascik is zero-config. Most sites never need bascik.config.ts. Requires the bascik skill for project basics.

Decide whether a config is needed

Create bascik.config.ts only after naming a concrete requirement that differs from a built-in default. Examples that justify one:

• components.external for third-party custom elements
• pipeline.exec for an existing lifecycle script (Tailwind, esbuild bundle, feed, search index)
• pipeline.watchPaths for helpers or content outside pages and components
• base for a subdirectory deployment
• scoping.attributes.class: false for Tailwind
• generate.sitemapLastmod, generate.cspHashes, or a custom minify.js
• contentSecurityPolicy to send a Content-Security-Policy header (see below)

If every value would equal a default, do not create the file. If one exists, keep only the non-default values. Run the audit after every edit: