Use static variable for `DATABASE_URL`

[hyunbinseo]

Is there a reason why the env.DATABASE_URL is dynamically imported?

This is the template generated with sv@0.6.11:

// current
import { env } from '$env/dynamic/private';
import Database from 'better-sqlite3';
import { drizzle } from 'drizzle-orm/better-sqlite3';

if (!env.DATABASE_URL) throw new Error('DATABASE_URL is not set');
const client = new Database(env.DATABASE_URL);
export const db = drizzle(client);

This is what I've been using:

// proposal
import { DATABASE_URL } from '$env/static/private';
import Database from 'better-sqlite3';
import { drizzle } from 'drizzle-orm/better-sqlite3';

const client = new Database(DATABASE_URL);
export const db = drizzle(client);

[benmccann]

I think dynamic is correct since credentials are generally provided at deploy time rather than build time

[hyunbinseo]

I guess I am too accustomed to the Node.js adapter and SQLite.

I used to specify the DATABASE_URL in the .env.production file.

process.env or $env/dynamic/private seems correct for general purpose.

Reference: Cloudflare Pages environment-variables and process.env docs.

[hyunbinseo]

At least for the SECRETS, the $env/dynamic/* seems to be the correct option.

---

Are there examples in the template where $env/static/* are used?

import { API_KEY } from '$env/static/private';
import { PUBLIC_BASE_URL } from '$env/static/public';

@benmccann Would be nice if there is a public .env file that can showcase this.

e.g. .env.public includes the SITE_NAME variable which can be statically referenced.

• chore: overhaul ignore configs kit#11938

---

It would also be nice if the env.DATABASE_URL is typed as string | undefined even if it is defined in the .env file.

This will nudge developers to check if the values are truthy on runtime, but I guess this is an SvelteKit issue.