Fails to load config with `Excepted identifier but found "import"` error #19018

zhangtao25 · 2024-12-20T06:24:07Z

Note: vite@6.0.5 is out pinning to esbuild 0.24.0 until @sapphi-red's PR to esbuild is merged and released, you can update to latest vite to fix this issue. Leaving this issue open as we'll revert the temporary fix soon.

Workaround and the cause

It seems a change in esbuild 0.24.1 is affecting Vite's config loader: evanw/esbuild#4010

The current workaround is to set overrides in package managers:

pnpm overrides

  "pnpm": {
    "overrides": {
      "esbuild": "0.24.0"
    }
  }

npm overrides

{
  "overrides": {
    "esbuild": "0.24.0"
  }
}

yarn resolutions

{
  "resolutions": {
    "esbuild": "0.24.0"
  }
}

Edited by @sapphi-red

Describe the bug

Reproduction

pnpm create vite@latest; babel-react

Steps to reproduce

No response

System Info

System:
    OS: macOS 15.0
    CPU: (8) arm64 Apple M1 Pro
    Memory: 144.56 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.3.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.9.0 - /usr/local/bin/npm
    pnpm: 9.15.0 - /usr/local/bin/pnpm
    bun: 1.1.28 - ~/.bun/bin/bun
  Browsers:
    Chrome: 131.0.6778.205
    Safari: 18.0
  npmPackages:
    @vitejs/plugin-react: ^4.3.4 => 4.3.4
    vite: ^6.0.3 => 6.0.4

Used Package Manager

pnpm

Logs

No response

Validations

Follow our Code of Conduct
Read the Contributing Guidelines.
Read the docs.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
The provided reproduction is a minimal reproducible example of the bug.

ocavue · 2024-12-20T06:26:16Z

This error can be reproduced by using pnpm create vite with the react template, shown below:


$ pnpm create vite
.../Library/pnpm/store/v3/tmp/dlx-81687  |   +1 +
.../Library/pnpm/store/v3/tmp/dlx-81687  | Progress: resolved 1, reused 1, downloaded 0, added 1, done
✔ Project name: … vite-project
✔ Select a framework: › React
✔ Select a variant: › TypeScript

Scaffolding project in /private/tmp/testvite3/vite-project...

Done. Now run:

  cd vite-project
  pnpm install
  pnpm run dev


$ cd vite-project

$ pnpm install
Packages: +182
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 224, reused 180, downloaded 2, added 182, done

dependencies:
+ react 18.3.1 (19.0.0 is available)
+ react-dom 18.3.1 (19.0.0 is available)

devDependencies:
+ @eslint/js 9.17.0
+ @types/react 18.3.18 (19.0.2 is available)
+ @types/react-dom 18.3.5 (19.0.2 is available)
+ @vitejs/plugin-react 4.3.4
+ eslint 9.17.0
+ eslint-plugin-react-hooks 5.1.0
+ eslint-plugin-react-refresh 0.4.16
+ globals 15.14.0
+ typescript 5.6.3 (5.7.2 is available)
+ typescript-eslint 8.18.1
+ vite 6.0.4

Done in 3.5s

$ pnpm run build

> vite-project@0.0.0 build /private/tmp/testvite3/vite-project
> tsc -b && vite build

✘ [ERROR] Expected identifier but found "import"

    (define name):1:0:
      1 │ import.meta.dirname
        ╵ ~~~~~~

✘ [ERROR] Expected identifier but found "import"

    (define name):1:0:
      1 │ import.meta.filename
        ╵ ~~~~~~

✘ [ERROR] Expected identifier but found "import"

    (define name):1:0:
      1 │ import.meta.url
        ╵ ~~~~~~

failed to load config from /private/tmp/testvite3/vite-project/vite.config.ts
error during build:
Error: Build failed with 3 errors:
(define name):1:0: ERROR: Expected identifier but found "import"
(define name):1:0: ERROR: Expected identifier but found "import"
(define name):1:0: ERROR: Expected identifier but found "import"
    at failureErrorWithLog (/private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:1476:15)
    at /private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:945:25
    at runOnEndCallbacks (/private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:1316:45)
    at buildResponseToResult (/private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:943:7)
    at /private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:970:16
    at responseCallbacks.<computed> (/private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:622:9)
    at handleIncomingPacket (/private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:677:12)
    at Socket.readFromStdout (/private/tmp/testvite3/vite-project/node_modules/.pnpm/esbuild@0.24.1/node_modules/esbuild/lib/main.js:600:7)
    at Socket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:561:12)
 ELIFECYCLE  Command failed with exit code 1.

kurone-kito · 2024-12-20T06:50:07Z

I found the same problem in my environment, but the following command temporarily solved it.
I hope it works in your environment as well.

pnpm add -D esbuild@=0.24.0
pnpm dedupe

pga5e · 2024-12-20T06:51:45Z

+1 ran a totally new completely clean build in new pc and got this same error

0x2E · 2024-12-20T06:52:15Z

evanw/esbuild#4010

suhailkc · 2024-12-20T07:06:40Z

npm i -D esbuild@0.24.0

lingrottin · 2024-12-20T07:13:20Z

+1 but downgrading esbuild solves that 😸

sai-oduri · 2024-12-20T07:15:01Z

downgrade vite version working for now.
run this in your project directory
npm uninstall vite
npm i -D vite@5
or simply
npm i -D vite@5

CHMOSE023 · 2024-12-20T07:25:03Z

npm view create-vite versions --json

npm create vite@5.5.5

5.5.5 这个版本可用

Mxtzz · 2024-12-20T07:43:35Z

删除lock文件，删除node_modules，再pnpm install就会复现。

临时修复 pnpm i -D esbuild@0.24.0

huisam · 2024-12-20T07:44:57Z

please resolve this 🙏 🙏 I've just rollback to vite v5

wisnunugroho21 · 2024-12-20T07:47:54Z

seems like a bug from esbuild.
esbuild 0.24.1 has a bug.

sapphi-red · 2024-12-20T08:11:26Z

It seems a change in esbuild 0.24.1 is affecting Vite's config loader: evanw/esbuild#4010

The current workaround is to set overrides in package managers:

pnpm overrides

  "pnpm": {
    "overrides": {
      "esbuild": "0.24.0"
    }
  }

npm overrides

{
  "overrides": {
    "esbuild": "0.24.0"
  }
}

yarn resolutions

{
  "resolutions": {
    "esbuild": "0.24.0"
  }
}

om-baji · 2024-12-20T08:12:26Z

Downgrade to vite 5

MeowB · 2024-12-20T08:13:31Z

+1, downgraded to vite 5.5.5

zcodecn · 2024-12-20T08:54:30Z

I encountered the same error today. After changing Vite to version 5.4.11, it worked fine. It seems that version 6.0 is still unstable.

sameignatovich · 2024-12-20T09:10:05Z

Looks like fix on the way: evanw/esbuild#4013

akshaywritescode · 2024-12-20T09:13:42Z

it because of es build run "npm install -D vite@^5" on your project root, this version have stable esbuild

Azz-0179 · 2024-12-20T09:18:09Z

npm i -D esbuild@0.24.0

iamdanajr · 2024-12-20T09:27:49Z

It seems a change in esbuild 0.24.1 is affecting Vite's config loader: evanw/esbuild#4010

The current workaround is to set pnpm overrides to package.json:
  "pnpm": {
    "overrides": {
      "esbuild": "0.24.0"
    }
  }
You can use npm overrides or yarn resolutions as well.

Thanks, it's seem this is the only fix for now.

stormmuller · 2024-12-20T09:30:16Z

The override does not work in a mono repo

HumboldtK · 2024-12-20T09:43:42Z

Getting this same error when using terser.

breizh24 · 2024-12-20T09:47:48Z

On my project this override worked

{
  "name": "Your app",
  "devDependencies": {
    "vite": "^6.0.4",
  },
  "overrides": {
    "vite": {
      "esbuild": "0.24.0"
    }
  },
}

Then delete the node_modules folder and run npm install

Blankeos · 2024-12-20T10:27:47Z

Idk what made it work for me. I have a different project where Vite 6 works and I don't even get the above errors.

But on another project, it doesn't.

What I did:

# On my project that doesn't work...
rm -rf node_modules
bun install # or npm install
bun dev # it still didn't work. (weird)

# So to compare with the project that actually worked, I basically...
# 1. Committed my current package.json on the project that doesn't work.
# 2. REMOVED all the `dependencies` and `devDependencies` in the project that doesn't work, then replaced it with the `dependencies` and `devDependencies` of the project that works. (It doesn't matter if the packages don't match).
# 3. Then as usual, I did...
rm -rf node_modules
bun install
bun dev # And this time it worked, cool.
# 4. After that, I stashed the current package.json changes. Meaning it will become your current project's non-working package.json. Then as usual, I did this again...
rm -rf node_modules
bun install
bun dev # And it actually worked for the current project.

I can't even explain what happened. But if anyone's pulling their hair and looking for an alternative solution, hope this helps 😐

losertowinner · 2024-12-20T10:30:39Z

Same

urprakashgupta · 2024-12-20T10:55:59Z

I always need to run - npm i -D esbuild@0.24.0 when i create new react-vite project. Please solve this issue

iamdanajr · 2024-12-20T11:22:00Z

Workaround and the cause

It seems a change in esbuild 0.24.1 is affecting Vite's config loader: evanw/esbuild#4010

The current workaround is to set overrides in package managers:
pnpm overrides
  "pnpm": {
    "overrides": {
      "esbuild": "0.24.0"
    }
  }
npm overrides
{
  "overrides": {
    "esbuild": "0.24.0"
  }
}
yarn resolutions
{
  "resolutions": {
    "esbuild": "0.24.0"
  }
}
Edited by @sapphi-red

Describe the bug
### Reproduction pnpm create vite@latest; babel-react
Steps to reproduce

No response

System Info
System:
    OS: macOS 15.0
    CPU: (8) arm64 Apple M1 Pro
    Memory: 144.56 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.3.0 - /usr/local/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.9.0 - /usr/local/bin/npm
    pnpm: 9.15.0 - /usr/local/bin/pnpm
    bun: 1.1.28 - ~/.bun/bin/bun
  Browsers:
    Chrome: 131.0.6778.205
    Safari: 18.0
  npmPackages:
    @vitejs/plugin-react: ^4.3.4 => 4.3.4
    vite: ^6.0.3 => 6.0.4
Used Package Manager

pnpm

Logs

No response

Validations

Follow our Code of Conduct

Read the Contributing Guidelines.

Read the docs.

Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.

Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

The provided reproduction is a minimal reproducible example of the bug.

bun overrides

  "bun": {
      "overrides": {
        "esbuild": "0.24.0"
      }
    }

Vinayak-palya · 2024-12-20T11:33:50Z

downgrading vite version solves the above issue

patak-dev · 2024-12-20T11:38:50Z

vite@6.0.5 is out pinning to esbuild 0.24.0 until @sapphi-red's PR to esbuild is merged and released, you can update to latest vite to fix this issue

moto69 · 2024-12-20T11:53:59Z

Thank you very much. I am cured.

RubTalha · 2024-12-22T14:11:48Z

https://stackoverflow.com/a/79301134/13086128

rakuzen25 · 2024-12-22T14:32:34Z

Now that esbuild has released v0.24.2, is it possible to undo #19027?

zhangtao25 added the pending triage label Dec 20, 2024

This comment was marked as duplicate.

Sign in to view

zhangtao25 mentioned this issue Dec 20, 2024

Vite Version 6.0.4 is Not running in dev mode #19019

Closed

7 tasks

This comment was marked as duplicate.

Sign in to view

This comment was marked as spam.

Sign in to view

This comment was marked as duplicate.

Sign in to view

This comment was marked as spam.

Sign in to view

sapphi-red added bug: upstream Bug in a dependency of Vite p5-urgent Fix build-breaking bugs affecting most users, should be released ASAP (priority) labels Dec 20, 2024

sapphi-red mentioned this issue Dec 20, 2024

Error while upgrading from v5 to v6 #19021

Closed

7 tasks

github-actions bot removed the pending triage label Dec 20, 2024

sameignatovich mentioned this issue Dec 20, 2024

Error when running Vite with import.meta in vite.config.js #19024

Closed

7 tasks

This comment was marked as spam.

Sign in to view

deenuit113 mentioned this issue Dec 20, 2024

Excepted identifier but found "import" 오류 6ITAll/book-it-da#49

Merged

This comment was marked as spam.

Sign in to view

RitsukiKagerou mentioned this issue Dec 20, 2024

Error Install new Jetstream with Livewire laravel/jetstream#1556

Closed

pepijnve mentioned this issue Dec 20, 2024

Vaadin 24.6.0 doesn't compile the frontend, downgrade to 24.5.8 works as usually vaadin/platform#7139

Closed

infomiho mentioned this issue Dec 20, 2024

Fix esbuild 0.24.1 issue wasp-lang/wasp#2425

Closed

KonradHoeffner mentioned this issue Dec 20, 2024

build fail due to esbuild 0.24.1 dependency #19026

Closed

7 tasks

patak-dev mentioned this issue Dec 20, 2024

fix: esbuild regression (pin to 0.24.0) #19027

Merged

jpaquim mentioned this issue Dec 20, 2024

Import failing during build antfu-collective/vite-plugin-inspect#125

Closed

7 tasks

vadimpiven mentioned this issue Dec 20, 2024

Dependancy update platforma-open/star-read-mapping#18

Merged

JurgenThijs mentioned this issue Dec 20, 2024

Expected identifier but found "import" laravel/framework#53991

Closed

tkuijer mentioned this issue Dec 20, 2024

[Bug]: Unable to "npm run dev" on empty new JetStream project beyondcode/herd-community#1211

Open

Fails to load config with Excepted identifier but found "import" error #19018

Fails to load config with Excepted identifier but found "import" error #19018

Comments

zhangtao25 commented Dec 20, 2024 • edited by patak-dev Loading

Describe the bug

Reproduction

Steps to reproduce

System Info

Used Package Manager

Logs

Validations

ocavue commented Dec 20, 2024

This comment was marked as duplicate.

This comment was marked as duplicate.

This comment was marked as duplicate.

This comment was marked as duplicate.

kurone-kito commented Dec 20, 2024

pga5e commented Dec 20, 2024

0x2E commented Dec 20, 2024

This comment was marked as spam.

suhailkc commented Dec 20, 2024

This comment was marked as spam.

lingrottin commented Dec 20, 2024

sai-oduri commented Dec 20, 2024

This comment was marked as duplicate.

CHMOSE023 commented Dec 20, 2024

This comment was marked as spam.

Mxtzz commented Dec 20, 2024

This comment was marked as spam.

huisam commented Dec 20, 2024

wisnunugroho21 commented Dec 20, 2024

This comment was marked as spam.

sapphi-red commented Dec 20, 2024 • edited Loading

om-baji commented Dec 20, 2024

MeowB commented Dec 20, 2024

zcodecn commented Dec 20, 2024

sameignatovich commented Dec 20, 2024

akshaywritescode commented Dec 20, 2024

Azz-0179 commented Dec 20, 2024

iamdanajr commented Dec 20, 2024 • edited Loading

stormmuller commented Dec 20, 2024

This comment was marked as spam.

This comment was marked as spam.

HumboldtK commented Dec 20, 2024

breizh24 commented Dec 20, 2024

Blankeos commented Dec 20, 2024 • edited Loading

losertowinner commented Dec 20, 2024

urprakashgupta commented Dec 20, 2024

iamdanajr commented Dec 20, 2024

Describe the bug

Steps to reproduce

System Info

Used Package Manager

Logs

Validations

Vinayak-palya commented Dec 20, 2024

patak-dev commented Dec 20, 2024

moto69 commented Dec 20, 2024

RubTalha commented Dec 22, 2024

rakuzen25 commented Dec 22, 2024

Fails to load config with `Excepted identifier but found "import"` error #19018

Fails to load config with `Excepted identifier but found "import"` error #19018

zhangtao25 commented Dec 20, 2024 •

edited by patak-dev

Loading

sapphi-red commented Dec 20, 2024 •

edited

Loading

iamdanajr commented Dec 20, 2024 •

edited

Loading

Blankeos commented Dec 20, 2024 •

edited

Loading