top-level target option

[danielroe]

Describe the feature

There are quite a few different locations where target is relevant, including within both nitro rollup, nitro esbuild, vite esbuild, vite optimizeDeps esbuild, vite target, etc. (And the vite options are doubled as the config is used both on client and server.)

It would be handy to have a central place to set a build target and have it set in all the appropriate places.

Possibly relevant: #14601

Usage

import { defineNuxtConfig } from 'nuxt'

export default defineNuxtConfig({
  target: {
    client: ['es2020'],
    server: ['es2019']
  },
  // or
  build: {
    target: { /* */ }
  }
})

Additional information

• Would you be willing to help implement this feature?
• Could this feature be implemented as a module?

Final checks

• Read the contribution guide.
• Check existing discussions and issues.

[pi0]

I like the idea! Only some points:

• Since both build.* and target are Nuxt 2 options, we might find better namespace. I would suggest clientTarget and serverTarget top level options or buildTarget: { client, server }
• We need to create a list of supported targets that is limited than ESBuild and is mappable to different bundlers.
• Possible supported targets will be changed over the time in order to only support ever-green browsers. How do you imagine to handle this?

[marr]

I'm also wondering about the vite.build.target setting. I am getting the same error as the creator of the issue linked above, after trying to use arquero in my project.

[manniL]

Also related: nuxt/framework#7717