👋 Want to contribute to vercel/next.js?
If you have a bug or an idea, read the contributing guidelines before opening an issue.If you're ready to tackle some open issues, we've collected some good first issues for you.
Issues
Search Issues
is:issue memory leak build
Search results
- Status: Open.#89091 In vercel/next.js;
- Status: Open.#44685 In vercel/next.js;
- Status: Open.#85666 In vercel/next.js;
- Status: Open.#76704 In vercel/next.js;
- Status: Open.#84884 In vercel/next.js;
- Status: Open.#83275 In vercel/next.js;
- Status: Open.#54708 In vercel/next.js;
- Status: Closed (completed).#89033 In vercel/next.js;
- Status: Open.#76710 In vercel/next.js;
- Status: Open.#67647 In vercel/next.js;
- Status: Open.#51404 In vercel/next.js;
- Status: Open.#82511 In vercel/next.js;
- Status: Not planned (skipped).#66696 In vercel/next.js;
- Status: Open.#64921 In vercel/next.js;
- Status: Closed (completed).#80779 In vercel/next.js;
- Status: Open.#84648 In vercel/next.js;
- Status: Open.#69865 In vercel/next.js;
- Status: Open.#60473 In vercel/next.js;
- Status: Closed (completed).#79588 In vercel/next.js;
- Status: Closed (completed).#89542 In vercel/next.js;
- Status: Closed (completed).#89090 In vercel/next.js;
- Status: Duplicate of an existing item.#75686 In vercel/next.js; · Duplicate
- Status: Closed (completed).#75314 In vercel/next.js;