Bug: Inconsistent "Expected never, received array" in v2

Environment:

Node 12.18.2 Webpack 4.44.2 Zod 2.0.0-beta.21

// tsconfig.json
// target: commonjs2
{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es2019",
    "lib": ["es2020"],
    "strict": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "noImplicitThis": true,
    "alwaysStrict": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": false,
    "inlineSourceMap": true,
    "inlineSources": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "strictPropertyInitialization": false,
    "typeRoots": ["./node_modules/@types", "./typings"]
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "**/*.test.ts", "**/*.it.ts"]
}

Error

I’m experiencing the following error when the parser encounters an unknown field: Expected never, received array.

The weirdest thing is that this does not happen in local development, but it only happens when files are bundle with webpack and production mode.

Expected result

According to v2 doc: By default Zod object schema strip unknown keys from the output.

Code

Here’s a snippet of code that I have:

const atAgencySchema = z
  .object({
    agencyId: z.string(),
    market: z.enum(['X', 'Y', 'Z']),
    name: z.string(),
  })

// ...
const record = { agencyId: 'id', market: 'Y', name: 'yo', skills: ['1'] } 
atAgenciesSchema.parse(record) // throws "Expected never, received array"

Workaround

Reverted back to v1, and used nonstrict()

[mmeylan]

Awesome, thanks for the great work @colinhacks

[colinhacks]

Okay I’ve identified the problem! Very silly mistake on my part in the parsing logic. Fixed in beta 22. Thanks for the great repro @mmeylan.