519 issues found — filter by difficulty, status, or repo
Flaky test requires investigation into undo behavior during publishing.
High memory usage in development mode requires deep investigation and Next.js expertise.
HTTP status codes are incorrect when streaming is blocked and layout.js is present.
Persistent Chrome DevTools port disconnection issue with unclear root cause.
The issue is not considered a bug by maintainers and has low priority.
The issue involves fixing a missing doctype name in breadcrumbs on the tree view.
Issue involves complex async behavior and module registration in Node.js core.
Playwright tests failing with undefined property error during cleanup
Media queries in custom CSS for Gutenberg blocks are not being applied correctly.
The issue involves a build loop in the vips package during branch changes.
The issue involves a specific Node.js version interaction with fetch that crashes on error responses.
The issue involves mobile-specific behavior and timing-sensitive rendering.