# Parsing ecmascript source code failed How to fix it.

URL: https://antideploy.com/blog/parsing-ecmascript-source-code-failed

The compiler could not read one of your source files. It is normally a syntax error, and the lines above name the file and the column.

**What you see**

```
./src/app/page.tsx:15:3
Parsing ecmascript source code failed
> 15 |   <div className="card">
     |   ^
Expected '</', got 'jsx text'
```

## At a glance

- **What it means**: A syntax error in a source file
- **Where to look**: The file and column above the message
- **Test locally**: Run npm run build
- **The fix**: Correct the syntax

Published 7 October 2026. Facts checked 7 October 2026. 1 min read.

## What it means

The bundler tried to read one of your files and could not understand it. It is normally a plain syntax error: a missing bracket, an unclosed tag, a stray character. A local build would have caught the same error.

## How to fix it

### 1. Read the file and column above the message

The lines above point at the file and the position.

### 2. Run the build on your machine

Run `npm run build`. If it fails the same way, fix that error first.

### 3. Check for a half-edited file

A coding agent can leave a file half edited, with a tag or bracket opened and never closed. Ask it to fix the syntax in that file.

## Syntax questions, answered.

Anything else? Write to us and a person answers.

[support@antideploy.com](mailto:support@antideploy.com)

### Why did it work in dev mode?

Dev mode compiles a page when you open it. If you did not open that page, the error did not show.

### Does this failed deploy cost anything?

No. Failed deploys never count against your plan.

### What if I cannot see the error?

Run `npm run build` on your machine. The terminal prints the file, the line and the column, with a pointer to the exact character.

## More guides, and the platform.

Each platform page covers one part of Antideploy: what it does, where it stops and the questions people ask. [See the whole platform](https://antideploy.com/platform), or [all the guides](https://antideploy.com/blog).

- [Next.js build worker exited with code: 1](https://antideploy.com/blog/nextjs-build-worker-exited-with-code-1): The build worker crashed. Read the lines above for the file, run the build locally, and check memory.
- [TypeScript error fails the build](https://antideploy.com/blog/typescript-error-fails-the-build): A type error stops the build even when the app runs locally in dev mode. Run the type check and fix it.
- [Module not found: Can't resolve](https://antideploy.com/blog/module-not-found-cant-resolve): The build cannot find an import. Match capital letters exactly, add the package, or commit the file.

- [Deployments](https://antideploy.com/platform/deployments)
- [Logs and monitoring](https://antideploy.com/platform/logs-and-monitoring)

Facts on this page were checked against the live platform on 7 October 2026.

## Deploy something. Start with one sentence.

Paste one sentence into your coding agent, click Approve once, and get a live link. No card, no trial clock.

To set this up, give your coding agent this sentence:

```text
Set this project up to deploy on Antideploy. Fetch https://antideploy.com/agent.md and follow it.
```