Uncaught ReferenceError: exports is not defined at version 3.3.18 and Parcel

Intended outcome:

The version of @apollo/client is upgraded from 3.3.17 to 3.3.18 safely and the built application is running without issues.

Actual outcome:

After upgrade and build without issues, the application fails from the start with a blank page and an error in console:

Uncaught ReferenceError: $24a7145fde937c9e5b0a055eaa64c5e1$exports is not defined

How to reproduce the issue:

• Set dependencies:

"@babel/core": "^7.10.1",
"@parcel/config-default": "^2.0.0-beta.1",
"@parcel/transformer-typescript-tsc": "^2.0.0-beta.1",
"@parcel/validator-typescript": "^2.0.0-beta.1",
"parcel": "^2.0.0-beta.1",
"@apollo/client": "3.3.18",

• Parcel config .parcelrc:

{
  "extends": "@parcel/config-default",
  "transformers": {
    "*.{ts,tsx}": ["@parcel/transformer-typescript-tsc"]
  }
}

• tsconfig.json

{
    "compilerOptions": {
        "target": "es6",
        "resolveJsonModule": true,
        "module": "commonjs",
        "jsx": "react",
        "outDir": "./dist",
        "rootDir": "./src",
        "strict": true,
        "moduleResolution": "node",
        "baseUrl": "./src",
        "paths": {
            "~/*": ["./*"]
        },
        "types": [
            "./src/models",
            "node",
            "jest"
        ],
        "esModuleInterop": true,
        "experimentalDecorators": true,
        "skipLibCheck": true
    },
    "exclude": ["dist/**", "node_modules/**.*"]
}

• Run build command npx parcel build src/index.html
• Run with Nginx (if it matters) and open in browser

Versions

System:
    OS: macOS 11.5
  Binaries:
    Node: 16.6.1 - /usr/local/bin/node
    Yarn: 1.22.10 - ~/stockX/viper/node_modules/.bin/yarn
    npm: 7.20.5 - /usr/local/bin/npm
  Browsers:
    Chrome: 92.0.4515.159
    Firefox: 90.0.2
    Safari: 14.1.2
  npmPackages:
    @apollo/client: 3.3.18 => 3.3.18 
    @apollo/link-error: ^2.0.0-beta.3 => 2.0.0-beta.3 
    apollo: ^2.31.0 => 2.32.1 
    react-apollo: 3.1.5 => 3.1.5

I assume that this PR that corresponds this patch may still miss some side effects and should include some dependencies to avoid their truncation. Since I have the same error but on other line of code if upgrading to 3.4.8, I assume that there could be more side effects.

[irenlian]

I also searched for onClearStore throughout the codebase, we don’t use it. So I hope it is not the reason.

[benjamn]

@irenlian Can you share the stacktrace leading to that ReferenceError?