Use esbuild to build server-side code

[emmatown]

Requires #7805

While reviewing #7744 - the pirates changes demonstrated that we should simplify the build process for end developer configurations.

Keystone passes compiling to next/babel at the moment, but that is executed in a way that isn't actually helping us drop the responsibility, nor the maintenance burden. We are operating in a constrained environment, with no configuration options for our users. This could be simpler.

Some options

• tsc, slower 🐌 , no bundling 😶‍🌫️
• esbuild, fast 💨, easy bundling 📦, limited configuration ❤

This pull request switches @keystone-6/core to use esbuild for the compilation process.

This change should ideally not break most users, the reality of modules in the JS ecosystem is that every tools does things ever so subtly different so there will likely be small breaks, the most notable change though is that __dirname, __filename, and require.resolve will not be treated specially, this essentially means in most cases, they should just be avoided. If you need to read a file/etc., you should do it relative to process.cwd().

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Sep 9, 2022 at 11:39AM (UTC)

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 8cdf849:

Sandbox	Source
@keystone-6/sandbox	Configuration

[jlarmstrongiv]

Following up from Slack, are the new functions loadBuiltConfig, getBuiltConfigPath, and getAdminPath exported from any part of the @keysone-6/core package (such as @keystone-6/core/system or @keystone-6/core/artifacts)? It’s very important to have those functions exposed.

[dcousens]

Hi @jlarmstrongiv, I don't think they are and we typically want to be conservative in what we export. Did you have a particular use case in mind?

[jlarmstrongiv]

@dcousens Ahh, I had missed that initConfig was already exported. I can redefine what’s not included 👍

I’m building my own “start” function to return the underlying express server for experimental aws lambda support and bundling. If I can get that to work, then I should be able to make a pr for an experimental generateExpressApp and a bundling example. Supporting serverless (even just experimentally or a community example) would be very nice and I think it’s doable.

[emmatown]

Before merging this, we should make sure source maps work (we might want to skip source maps for the prod build but they should definitely work in dev)

[emmatown]

Source maps turned into a rabbit hole, doing it Correctly would be very subtle so let's go with no source maps for now rather than wrong source maps. The bundle that esbuild generates is reasonably readable so I don't think it's a huge concern.