Failed to parse source map

[creage]

Using zod: 3.11.6

We are having warning in index.mjs

WARNING in ./node_modules/zod/lib/index.mjs
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from 'C:\repos\Git\WorkZone\WZ-Teams\Source\tabs\node_modules\zod\src\types.ts' file: Error: ENOENT: no such file or directory, open 'C:\repos\Git\WorkZone\WZ-Teams\Source\tabs\node_modules\zod\src\types.ts'

apparently the referenced src\types.ts is not shipped with package, leading to such error.

[ingro]

Can confirm that too, the index.mjs.map references files in the src folder

[scotttrinh]

PRs welcome to fix this in a way that is consistent with what other libraries provide here. I'm not personally very familiar with common practice in this regard.

[adnan-sheikh]

Even i'm getting same errors.

[jer-sen]

Same issue here, don't known how to fix that. Issue with build script?

[evantrimboli]

I'm having the same issue. For reference, this has been discussed before: #20

I'm using CRA and it doesn't offer the option to configure the source-map-loader.

[colinhacks]

Can someone make a reproduction repo and share a link here? Issues with modules/imports such as this one require a lot of detail to reproduce: your language JS vs TS, module system (package.json "module" field value), Node version, bundler + version, etc. It easiest for maintainers to start with a rep we can use to reproduce.

[PawelJ-PL]

I've prepared basic example (based on Create React App): https://github.com/PawelJ-PL/zod_issue_828. The only change is that I added zod: PawelJ-PL/zod_issue_828@b43f7d9.

Just run yarn start or yarn build

[zerosheepmoo]

Hello, especially to CRA user.

I don't know why but zod is not going well with react-scripts 5.x.x.
so, I changed it to 4.0.3 and it works well!

Till the zod developer team resolve this issue, it is needed to config manually when do CRA :)

{
...
   "dependencies": {
      ...
      "react-scripts": "4.0.3",
      ...
   },
...
}

[PawelJ-PL]

react-scripts 5.0.0 introduced Webpack 5, so it's probably reason. As temporary workaround I disabled generating source map in my project (GENERATE_SOURCEMAP=false) so I didn't need do downgrade react-scripts

[alspdx]

react-scripts 5.0.0 introduced Webpack 5, so it's probably reason.

react-scripts 5.0.0 also adds source-map-loader to the Webpack configuration, which is where this error is originating. It is possible to configure Webpack to ignore warnings but that might not be the best default configuration for CRA. Looks like #864 will take care of it.

[colinhacks]

For the moment I removed source maps. Shipping ts files in the bundle isn't a great solution - it bloats the bundle and causes issues with certain build pipelines.