Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edge from 2050 to 2051 not found! #8632

Closed
yrral86 opened this issue Nov 15, 2022 · 6 comments
Closed

Edge from 2050 to 2051 not found! #8632

yrral86 opened this issue Nov 15, 2022 · 6 comments
Labels
Stale Inactive issues

Comments

@yrral86
Copy link

yrral86 commented Nov 15, 2022

    After upgrading to 2.8.0, I am seeing
馃毃 Build failed.

@parcel/bundler-default: Edge from 2050 to 2051 not found!

  Error: Edge from 2050 to 2051 not found!
      at ContentGraph.removeEdge (/redacted/node_modules/@parcel/graph/lib/Graph.js:156:13)
      at MutableBundleGraph.createBundleGroup (/redacted/node_modules/@parcel/core/lib/public/MutableBundleGraph.js:134:24)
      at decorateLegacyGraph (/redacted/node_modules/@parcel/bundler-default/lib/DefaultBundler.js:159:35)
      at Object.bundle (/redacted/node_modules/@parcel/bundler-default/lib/DefaultBundler.js:126:7)
      at BundlerRunner.bundle (/redacted/node_modules/@parcel/core/lib/requests/BundleGraphRequest.js:288:23)
      at async Object.run (/redacted/node_modules/@parcel/core/lib/requests/BundleGraphRequest.js:156:17)
      at async RequestTracker.runRequest (/redacted/node_modules/@parcel/core/lib/RequestTracker.js:756:20)
      at async Object.run (/redacted/node_modules/@parcel/core/lib/requests/ParcelBuildRequest.js:56:7)
      at async RequestTracker.runRequest (/redacted/node_modules/@parcel/core/lib/RequestTracker.js:756:20)
      at async Parcel._build (/redacted/node_modules/@parcel/core/lib/Parcel.js:400:11)

Originally posted by @yrral86 in #8554 (comment)

Downgrading to 2.7.0 results in a successful build.

@flavio-b
Copy link

I got the same error after upgrading to 2.8.0.

@mischnic
Copy link
Member

Can someone please provide a reproduction?

@yrral86
Copy link
Author

yrral86 commented Nov 17, 2022

I'm dealing with an app with 100s of thousands of lines that I'm trying to upgrade from parcel 1. I'm currently chasing another issue with version 2.7.0, but later I can try a build with --detailed-report and --log-level verbose to see if that gets me anything helpful. Do you have any other tips for getting more information to help narrow it down?

@flavio-b
Copy link

I've just tried updating my project from Parcel 2.7.0 to 2.8.0 again.

Running serve and build commands work successfully now. I have no idea what fixed it. Maybe, some deep dependency that got updated in the last couple of days. FYI, project only contains SCSS, CSS, HTML, plain JS and images. Essentially, it's based on this Bootstrap & Parcel tutorial.

@yrral86
Copy link
Author

yrral86 commented Nov 17, 2022

I'm not sure what is different this time (possibly tsconfig?), but I'm now seeing this:

console: type: css
console: type: css
馃毃 Build failed.

@parcel/namer-default: Bundle group cannot have more than one entry bundle of 
the same type

  AssertionError [ERR_ASSERTION]: Bundle group cannot have more than one entry 
  bundle of the same type

I added some logging to DefaultNamer.js and all I was able to figure out was that the ones with the error are type = css.

Rolling back to 2.7.0 resolves the error, but then I'm back to Could not resolve bundle with id when registering the service-worker.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.

@github-actions github-actions bot added the Stale Inactive issues label May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale Inactive issues
Projects
None yet
Development

No branches or pull requests

3 participants