Error: Got unexpected undefined

[chin2km]

🐛 bug report

Trying to migrate a very large repository (private to a company) from webpack to parcel, I'm facing this frequent build error Error: Got unexpected undefined when running parcel watch and the error log doesn't say much more than that. After adding some manual error logging at the source in parcel core in node module I have some more info. Its getting thrown when running svg,jpg,png files through the compressors in this function in @pracel/core.

We loved parcel in our tests and plan to use parcel in dev mode as of now (with plan to use in production later), but this error blocks us. Tried several fixes suggestion from various issues in the repo already but none seems to fix this particular issue.

Any suggestions/help to get around this is highly appreciated.

example complete error

 console: >> errorrrr {
   filePath: 'packages/application-desktop/dist/assets/apple-app-store-badge_nl.8fed9113.svg',
   err: Error: Got unexpected undefined
       at nullthrows (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/nullthrows/nullthrows.js:7:15)
       at Object.run (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/@parcel/core/lib/requests/DevDepRequest.js:133:54)
       at RequestTracker.runRequest (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/@parcel/core/lib/RequestTracker.js:725:34)
       at Object.runRequest (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/@parcel/core/lib/RequestTracker.js:777:23)
       at runDevDepRequest (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/@parcel/core/lib/requests/DevDepRequest.js:127:13)
       at runCompressor (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/@parcel/core/lib/requests/WriteBundleRequest.js:240:47)
       at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
       at async Promise.all (index 0)
       at async writeFiles (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/@parcel/core/lib/requests/WriteBundleRequest.js:207:3)
       at async Object.run (/Users/chintu.mohandas/Documents/Company/frontend-web/node_modules/@parcel/core/lib/requests/WriteBundleRequest.js:179:3) {
     framesToPop: 1
   },
   compressors: [
     {
       plugin: [Object],
       version: '2.7.0',
       resolveFrom: 'node_modules/@parcel/config-default/index.json',
       range: undefined,
       name: '@parcel/compressor-raw',
       keyPath: '/compressors/*/0'
     }
   ]
 }

The error happens when the svg,jpg,png files are run through @parcel/compressor-raw. Is there a way to skip using any compressor at all during dev mode?

.parcelrc

{
  "extends": [
    "@parcel/config-default"
  ],

  "resolveFrom": ".",
}

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

package.json

"scripts": {
    "client:dev": "parcel watch --target=client",
    "server:dev": "parcel watch --target=server",
    "develop:beta": "concurrently 'yarn client:dev' 'yarn server:dev'"
  },
  "targets": {
    "client": {
      "context": "browser",
      "source": "./src/index.html",
      "distDir": "./dist/assets",
      "publicUrl": "/assets/"
    },
    "server": {
      "context": "node",
      "outputFormat": "esmodule",
      "source": "./src/server-entry.tsx",
      "distDir": "./dist/server",
      "publicUrl": "/assets/",
      "includeNodeModules": false,
      "sourceMap": true
    }
  },

🤔 Expected Behavior

No errors in final compression stage

😯 Current Behavior

Described above

💁 Possible Solution

A Way to skip compressors for file globs?

🔦 Context

We are trying a build a very large server rendered react application with parcel.

💻 Code Sample

Happens in a private repo.

🌍 Your Environment

Software	Version(s)
Parcel	2.7.0
Node	16.14.2
npm/Yarn	yarn 1.22.19
Operating System	macOS Mac M1 Pro

[sznowicki]

It seems it's happening only on ARM. We're debugging the same problem over here. Same codebase, works on Intel Mac, doesn't work on M1 Mac.

[sznowicki]

Our debugging so far showed that it's somewhat related to how parcel uses cache.

We have a massive file that exports around 1000 react components. When we comment all exports out, it works in a dev mode. Then if we uncomment group by group it still works. After uncommenting around 300 exports, it still works, then we stop the dev process, rm -rf .parcel-cache and again parcel throws that error OP posted.

It feels like there's some sort of overflow somewhere. Weird it's only on ARM though.

[chin2km]

@sznowicki I can confirm most of that. This seems to happen only on M1 Mac. And ours is also a huge mono-repo with tons of JS and static assets file.

I also thought its mostly related to cache, but I run into the same issue even with --no-cache flag.

Already tried things like setting PARCEL_WORKER_BACKEND=process and PARCEL_WORKERS and various combination of .parcelrc but none seems to fix these issues.

[sznowicki]

From my observation "no-cache" makes it even worse. I suspect there's some weird memory problem. By "related to cache" I meant that if more is cached then problem disappears.

[sznowicki]

Now I got the same errors on my Intel Mac.

What changed is only we updated a dependency which holds all our corporate icons. The file count grew from ~1200 files to > 2400.

It worked until I changed the version of this dependency from 1.0.0-dev.1 to 1.0.0. From now on I get those unexpected undefined too.

Eventually I got it working:

1. start dev -> fail
2. start again -> fail
3. start again -> works
4. remove .parcel-cache -> start again -> still works

ARM Mac fails consistently. It really feels like some odd race condition somewhere.

[chin2km]

1. start dev -> fail
2. start again -> fail
3. start again -> works
4. remove .parcel-cache -> start again -> still works

same for me. But if you remove the dist folder in addition to .parcel-cache the fails starts over.
Overall in my tries I only had 10-20% success-rate when starting dev mode.

ARM Mac fails consistently

Same.

[andrewvmail]

I have a project that ran fine on an M1 mac 16GB and get this error on an M1 mac 8GB...

[sznowicki]

We did some additional tests and it really seems like if you try enough times it eventually builds up enough cache to not expose this (probable) memory issue and start the dev process (with PARCEL_WORKER_BACKEND=process).

We just tried it on Intel and ARM Macs. After 5 - 6 times of starting parcel it finally took off.

[MSpiechowicz]

Within one project with a lot of files using this flag PARCEL_WORKER_BACKEND=process helps, but in the other which does not have this amount of files it does not help and the same issue appears.

I would say that this is a major bug related to the M1 architecture or some memory leak/optimization.

[eMerzh]

hye, just shiming in, but i'm trying to upgrade some outdated repo to current version of parcel, and in the process i stumble upon this too...

i'm on mac intel, so it's not just arm....

also suspect memory/file count/size related... not much else to suggest atm ... still digging

[HcroakerDev]

Still getting this issue on parcel v2.8.0. Any idea on how to fix?

[mischnic]

Please share a reproduction if you have a situation where this happens consistently. That would help with getting this fixed

[gorakong]

possible fix: #6644