Top-level await is not available in the configured target environment ("es2020")

Describe the bug

When trying to build for netlify, I get the following error:

8:43:48 PM: .svelte-kit/output/server/chunks/db.js:40:11: ERROR: Top-level await is not available in the configured target environment (“es2020”)

I’ve set my build target to “esnext” in the vite.config.js, as instructed by sveltekit:

import { sveltekit } from '@sveltejs/kit/vite';

/** @type {import('vite').UserConfig} */
const config = {
  build: {
    target: 'esnext'
  },
  plugins: [sveltekit()]
};

export default config;

It would seem as though my target build env is being ignored.

Reproduction

Not sure how to do this, sorry - it’s a private repository. It’s a basic svelte app, however. On Node 18.7.0

Logs

8:43:48 PM: 
8:43:48 PM: > Using @sveltejs/adapter-netlify
8:43:48 PM: ✘ [ERROR] Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM:     .svelte-kit/output/server/chunks/db.js:40:11:
8:43:48 PM:       40 │ const db = await createRxDatabase({
8:43:48 PM:          ╵            ~~~~~
8:43:48 PM: ✘ [ERROR] Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM:     .svelte-kit/output/server/chunks/db.js:47:0:
8:43:48 PM:       47 │ await db.addCollections({
8:43:48 PM:          ╵ ~~~~~
8:43:48 PM: error during build:
8:43:48 PM: Error: Build failed with 2 errors:
8:43:48 PM: .svelte-kit/output/server/chunks/db.js:40:11: ERROR: Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM: .svelte-kit/output/server/chunks/db.js:47:0: ERROR: Top-level await is not available in the configured target environment ("es2020")
8:43:48 PM:     at failureErrorWithLog (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1566:15)
8:43:48 PM:     at /opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1024:28
8:43:48 PM:     at /opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:969:67
8:43:48 PM:     at buildResponseToResult (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1022:7)
8:43:48 PM:     at /opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:1134:14
8:43:48 PM:     at responseCallbacks.<computed> (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:671:9)
8:43:48 PM:     at handleIncomingPacket (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:726:9)
8:43:48 PM:     at Socket.readFromStdout (/opt/build/repo/node_modules/@sveltejs/adapter-netlify/node_modules/esbuild/lib/main.js:647:7)
8:43:48 PM:     at Socket.emit (node:events:513:28)
8:43:48 PM:     at addChunk (node:internal/streams/readable:324:12)
8:43:48 PM: ​
8:43:48 PM: ────────────────────────────────────────────────────────────────
8:43:48 PM:   "build.command" failed                                        
8:43:48 PM: ────────────────────────────────────────────────────────────────

System Info

My OS has no impact here, how would I get this info from netlify?

Severity

blocking an upgrade

Additional Information

Unable to deploy the site currently.

[kirkbushell]

What’s the config of your adapter, i.e. how does your svelte.config.js look like? If there’s edge: true in it, that’s the reason: most edge environments (Netlify etc) do NOT support top level await yet.

Mate, you hit the nail on the head - the issue was the edge: true configuration. There’s no way I would have worked that out lol

Ty so much for your time and help today - you are a gentleman and a scholar.

[dummdidumm]

What’s the config of your adapter, i.e. how does your svelte.config.js look like? If there’s edge: true in it, that’s the reason: most edge environments (Netlify etc) do NOT support top level await yet.