Parcel: Circular Dependency Issue

[scrossan-crown]

🐛 bug report

The issue I am having is when there are circular dependencies in my app and I am using npx parcel index.html command to run a dev server. The file is executed multiple times untill the maximum call stack size is exceeded.

{
  "presets": ["env", "react"],
  "plugins": [
    ["transform-runtime", {
      "polyfill": false,
      "regenerator": true
    }]
  ]
}

🤔 Expected Behavior

Parcel rebuilds the javascript and the file is only executed once

😯 Current Behavior

The file is executed multiple times untill the maximum call stack size is exceeded.

🔦 Context

I am having to change the file structure of my app to avoid this issue

🌍 Your Environment

| Software | Version(s) |
| ---------------- | ---------- |
| Parcel | 1.9.0
| Node | 10.0.0
| npm/Yarn | 6.1.0
| Operating System | Debian GNU/Linux 9 (stretch)

[DeMoorJasper]

I think this bug has already been reported, but it's definitely something that needs to be fixed.

I'll leave this open as I'm not sure if this is a duplicate.

[scrossan-crown]

Is there any idea on a time frame or is there a work around to not hot reload certain files and then on page refresh it would reload the file?

[lili21]

ran into this today. same issue.

[brookback]

I've got the same with Parcel 1.10.3 and with Typescript (external compile).

1. Run tsc -w
2. Run parcel index.html
3. Save .ts file in editor
4. Get error

build.06da9ca9.js:54 Uncaught RangeError: Maximum call stack size exceeded
    at localRequire (build.06da9ca9.js:54)
    at Object.parcelRequire.build/view/Header.js.react (Header.tsx:1)
    at newRequire (build.06da9ca9.js:49)
    at hmrAccept (index.tsx:7)
    at index.tsx:7
    at Array.some (<anonymous>)
    at hmrAccept (index.tsx:7)
    at index.tsx:7
    at Array.some (<anonymous>)
    at hmrAccept (index.tsx:7)

[droooney]

Yep, same here. Circular dependency along with hot reload causes this issue.

[wjustice]

Having the same issue.

[emadabdulrahim]

Having the same issue here. Is there any workaround for now?

[mischnic]

Duplicate of #1192