[FEATURE]: Upgrade esbuild in drizzle-kit to support es2023 target

[bagbag]

Running npx drizzle-kit generate errors with Invalid target "es2023" in "--target=es2023" in my project. Upgrading esbuild to the latest version solved that issue.

Describe what you want

Upgrading of esbuild to latest version.

[banuni]

also - esbuild < 0.22 has security issues and the ~ symbol disallows us to upgrade it manually in our repo...

reference: evanw/esbuild#3802

[ahalimkara]

We have the same issue, upgrading esbuild to 0.25.1 (latest as of writing) and drizzle-kit to 0.30.5 (latest as of writing) doesn't help. It only works when using target: ES2022

[dm-hadron]

Come on, guys. Upgrade it - the whole TS/JS world has moved on long time ago :-)

[Renato-dev13]

We have the same issue, upgrading esbuild to 0.25.1 (latest as of writing) and drizzle-kit to 0.30.5 (latest as of writing) doesn't help. It only works when using target: ES2022

Thanks for sharing! I’m facing the same issue. You mentioned it only works when using target: ES2022 — how exactly did you set that target? I'm really struggling with this and can't seem to make it work...

[ahalimkara]

Hi @Renato-dev13 , you just need to add target: ES2022 to tsconfig.json, example config:

{
    "compilerOptions": {
        "target": "ES2022",
        "module": "ES2022",
        "outDir": "dist",
        "moduleResolution": "Node",
        "skipLibCheck": true,
        "noUnusedLocals": true,
        "strict": true,
        "esModuleInterop": true,
        "resolveJsonModule": true
    },
    "include": ["src"]
}

[Renato-dev13]

Hi, @ahalimkara. Thanks for the quick reply!

[lifeordev]

+1, just ran into the same issue.

[ooau]

pLeASe FiX tHiS

[afogel]

+1

[andrewjmcgehee]

+1

[rbjakab]

Same issue.

[jmsofarelli]

+1

[trezi29]

+1

[GenericArt]

+1

[AndriiSherman]

will be included in the next release

[dinmukhamedm]

@AndriiSherman Hey thanks a lot for the fix!

I can see that in 0.31.0 the direct dependency on esbuild was bumped via #4416, but we still transitively depend on older esbuild, which causes the issue mentioned above:

also - esbuild < 0.22 has security issues

Which we get dependabot alerts for. I sort of think this must be a separate issue, but since you've worked on this recently, you probably have the best context.

The dependency chain in question is
[email protected] -> @esbuild-kit/[email protected] (deprecated) -> @esbuild-kit/[email protected] -> [email protected]

Also linking #4045 where people discuss the same issue and propose a possible fix

[oscar-ospina]

@AndriiSherman Hey thanks a lot for the fix!

I can see that in 0.31.0 the direct dependency on esbuild was bumped via #4416, but we still transitively depend on older esbuild, which causes the issue mentioned above:

also - esbuild < 0.22 has security issues

Which we get dependabot alerts for. I sort of think this must be a separate issue, but since you've worked on this recently, you probably have the best context.

The dependency chain in question is [email protected] -> @esbuild-kit/[email protected] (deprecated) -> @esbuild-kit/[email protected] -> [email protected]

Also linking #4045 where people discuss the same issue and propose a possible fix

x2

[kyleremotehands]

Dependabot cannot update esbuild to a non-vulnerable version
The latest possible version that can be installed is 0.18.20 because of the following conflicting dependencies:

[email protected] requires esbuild@~0.18.20 via a transitive dependency on @esbuild-kit/[email protected]
[email protected] requires esbuild@^0.25.2
No patched version available for esbuild
The earliest fixed version is 0.25.0.