build: Switch to esbuild

We will build all packages except the frontend (where vite remains in
use) with esbuild.

For some reason, the @yarnpkg/esbuild-plugin-pnp doesn't allow esbuild
to load esm modules and we fall back to commonjs for dependencies.
Hence we had to switch back to node_modules (but still rely on yarn
hardlinking for a more efficient install).

1 files changed, 0 insertions, 39 deletions

diff --git a/packages/main/vite.config.js b/packages/main/vite.config.js
deleted file mode 100644
index bdb0ca1..0000000
--- a/packages/main/vite.config.js
+++ /dev/null
@@ -1,39 +0,0 @@
-// @ts-check
-
-import { builtinModules } from 'module';
-
-import { makeConfig, node } from '../../config/vite-common';
-
-/** @type {string} */
-const PACKAGE_ROOT = __dirname;
-
-/**
- * @type {import('vite').UserConfig}
- * @see https://vitejs.dev/config/
- */
-const config = makeConfig({
-  root: PACKAGE_ROOT,
-  define: {
-    // Allow access to process.env in imported packages.
-    // https://github.com/vitejs/vite/issues/3176#issuecomment-876610206
-    'process.env': 'process["env"]',
-    'global.process.env': 'global.process["env"]',
-    'globalThis.process.env': 'globalThis.process["env"]',
-  },
-  build: {
-    target: node,
-    lib: {
-      entry: 'src/index.ts',
-      formats: ['cjs'],
-    },
-    rollupOptions: {
-      external: [
-        'electron',
-        'electron-devtools-installer',
-        ...builtinModules,
-      ],
-    },
-  },
-});
-
-export default config;