parcel: Cannot read property 'run' of undefined

πŸ› bug report

🚨  Cannot read property 'run' of undefined
    at /Users/nw/projects/motion/orbit/node_modules/parcel-bundler/lib/workerfarm/child.js:68:45
    at Generator.next (<anonymous>)
    at step (/Users/nw/projects/motion/orbit/node_modules/parcel-bundler/lib/workerfarm/child.js:3:191)
    at /Users/nw/projects/motion/orbit/node_modules/parcel-bundler/lib/workerfarm/child.js:3:437
    at new Promise (<anonymous>)
    at /Users/nw/projects/motion/orbit/node_modules/parcel-bundler/lib/workerfarm/child.js:3:99
    at Child.handleRequest (/Users/nw/projects/motion/orbit/node_modules/parcel-bundler/lib/workerfarm/child.js:75:7)
    at Child.messageListener (/Users/nw/projects/motion/orbit/node_modules/parcel-bundler/lib/workerfarm/child.js:36:19)
    at process.emit (events.js:185:15)
    at emit (internal/child_process.js:783:12)

πŸ€” Expected Behavior

This is on a small site I have working with 1.6.2, but 1.8.x seems to break. Mostly just would be helpful if there was more clear error messaging here so I could debug without binary searching.

🌍 Your Environment

Software Version(s)
Parcel 1.8.2
Node 9
Operating System high sierra

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 28 (13 by maintainers)

Commits related to this issue

Most upvoted comments

@designalchemy that’s probably why it’s failing, this line shouldn’t be used inside a plugin, as it might cause unwanted side-effects and is considered a private module/file within parcel and is being updated without keeping in mind semantic versioning: https://github.com/BoltDoggy/parcel-plugin-eslint/blob/7a0947bdec7d4552a68ce3a3bbcba339040a2db2/src/EslintAsset.js#L5

const JSAsset = require('parcel-bundler/src/assets/JSAsset');