Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

vercel / next.js Public

Notifications You must be signed in to change notification settings
Fork 27.7k
Star 129k

Code
Issues 2.7k
Pull requests 677
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

[Turbopack] make issue ordering stable#72751

Merged

sokra merged 2 commits intocanaryvercel/next.js:canaryfrom sokra/improve-issue-orderingvercel/next.js:sokra/improve-issue-orderingCopy head branch name to clipboard

Nov 14, 2024

+58-59

Conversation Commits2 (2)Checks Files changed

Commits

Commits on Nov 14, 2024

make issue ordering stable
sokra
committed
derive PartialOrd to avoid incorrect implementation
sokra
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.