[legacy-framework] Add support for blitz.config.ts

[flybayer]

Closes: blitz-js/legacy-framework#632

What are the changes and their implications?

Add support for blitz.config.ts. We use esbuild to bundle your blitz config file and output it at .blitz/blitz.config.js.

Feature Checklist

• Integration test added (see test docs if needed)
• Documentation added/updated (submit PR to blitzjs.com repo)
• Update recipe installer
• Test Vercel deployment

[andreasasprou]

Can this be disabled by default for non .ts files?

esbuild does not support features that need a type system, which are required for libraries like Typegoose.

[flybayer]

@andreasasprou so blitz.config.js is failing for you because emitDecoratorMetadata is in tsconfig even though blitz.config.js isn't importing any typescript? 🤔

[andreasasprou]

@flybayer

// blitz.config.js

/* eslint-disable @typescript-eslint/no-var-requires */
require('ts-node').register({ compilerOptions: { module: 'commonjs' } });
require('tsconfig-paths/register');
const { sessionMiddleware } = require('./session-middleware'); // TS file that creates a Typegoose model

const APP_BASE_PATH = process.env.APP_BASE_PATH || '/schedule';
const sentryConfig = require('./sentry.config');

module.exports = {
  basePath: APP_BASE_PATH,
  middleware: [...sessionMiddleware],
// ... etc

[sebastianhoitz]

@flybayer after upgrading to the new blitz.config.ts it looks like next/image has problems with custom registered domains. It complains they are not added to the config. Did some mapping get lost?

[flybayer]

@sebastianhoitz hmm, that's not expected. Can you open an issue?