Open stevejpurves opened 3 days ago
I've managed to work around this as follows, totally open to suggestions on a better way though, especially to avoid the hard type assignment.
// app-config.server.ts
import { loadValidatedConfig } from '@app-config/config';
import type { Config } from 'app-config';
let config: Awaited<ReturnType<typeof loadValidatedConfig>> | null = null;
export async function getConfig(): Promise<Config> {
if (!config) {
config = await loadValidatedConfig();
}
return config.fullConfig as unknown as Config;
}
// app-config.meta.yml
generate:
- { file: '@types/app-config/index.d.ts', augmentModule: false }
Hi There!
I've been migrating my application to use
@app-config/main
and have everthing working locally / in development but I hit problems when attempting to deploy to vercel. The specific error I am seeing is:I'm having a hard time tracking this down but wonder if it's a known/familiar issue when bundling for serverless (my application is remix.run built with vite)?
Alternatively, I am using
@app-config
but I'm not using encryption for secrets, in that case is it possible to exclude the@app-config/encryption
package by say using@app-config/config
directly? are potentially mitigating this issue?