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
#

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 130k

Code
Issues 2.7k
Pull requests 663
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

fix(next/image): undo tight coupling between `priority=true` and `fetchPriority=high`#67351

Merged

styfle merged 4 commits intocanaryvercel/next.js:canaryfrom styfle/remove-fetchpriority-highvercel/next.js:styfle/remove-fetchpriority-highCopy head branch name to clipboard

Jul 1, 2024

+45-23

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Jul 1, 2024

fix(next/image): undo tight coupling between priority=true and fetchPriority=high
styfle
committed
fix unit test
styfle
committed
fix integration tests
styfle
committed
fix one more test
styfle
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.