Fails to build zod v4 import for production

[loganzartman]

🐛 bug report

When importing anything from zod/v4, Parcel fails to emit a valid production bundle, with a runtime error like:

Uncaught ReferenceError: $99ddb65c04cf77f8$import$6c56dec3ecdf94f9 is not defined
    at index.js:4:16

This does not occur with the development server.

It seems to be related to scope hoisting, as --no-scope-hoist resolves the issue. Maybe this is similar to issues like #8792?

🎛 Configuration (.babelrc, package.json, cli command)

Default latest parcel configuration. See minimal repro: https://github.com/loganzartman/parcel-bug-zod-v4

🤔 Expected Behavior

There should be no runtime error when importing from zod/v4

😯 Current Behavior

Uncaught ReferenceError: $99ddb65c04cf77f8$import$6c56dec3ecdf94f9 is not defined
    at index.js:4:16

💁 Possible Solution

build with --no-scope-hoist

🔦 Context

Prevents using zod/v4

💻 Code Sample

https://github.com/loganzartman/parcel-bug-zod-v4

import {z} from 'zod/v4';

console.log(z.object({}));

🌍 Your Environment

Software	Version(s)
Parcel	2.15.2
Node	22.11.0
npm/Yarn	pnpm@9.13.2
Operating System	MacOS, Linux

[thobas-dnvgl]

Damn, wished I would have seen it sooner! I've spent my morning trying to find which of the dependencies I've upgraded broke my build (development is working fine) 😄.

[bacall213]

I'm also seeing this behavior with Rango when npm chooses zod versions >= 3.25.x. The build completes without error, but the resulting extension is broken.

@david-tejada - FYI for the renovate runs failing for Rango with zod 3.25+

https://github.com/david-tejada/rango/actions/runs/15610953084

[mdemblani]

I faced the same issue. In my case, it was a couple of things that played a part:

1. The import style:
   I had mixed up the import statements by doing the following:

   import * as z from 'zod'; // in file 1
   import { z } as 'zod';  // in file 2

   The solution was to use the * as z import statement
2. Missing the type property in package.json. Since the type field was missing, it was left purely to Parcel to decide how to parse a file as ESM or CJS. To resolve this added the following property to package.json file

   "type": "module",

Doing both of these ended up resolving the issue for good.

[thobas-dnvgl]

Thanks you @mdemblani! We already had "type": "module" but switching from import { z } as 'zod'; to import * as z from 'zod'; enabled us to upgrade both parcel and zod in our project.