rsnext/packages/next
Tim Neutkens 3f1a61b18f
Ensure content is kept rendered below the error overlay on build errors in new router (#41360)
- Remove unused code
- Keep rendering underlying component tree when there is a build error
- Move error catch up one level



## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have a helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have a helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm lint`
- [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
2022-10-12 14:36:24 +00:00
..
bin
build Fix CSS imports tree-shaking (#41357) 2022-10-12 13:41:19 +00:00
bundles
cli Refactor app dir related flags (#41166) 2022-10-04 22:16:44 +00:00
client Ensure content is kept rendered below the error overlay on build errors in new router (#41360) 2022-10-12 14:36:24 +00:00
compiled Handle error overlay for new router (#41325) 2022-10-11 16:11:57 +02:00
export Fix app static generation cases (#41172) 2022-10-06 21:43:23 +02:00
font Accept variable prop in google font loader (#41065) 2022-09-30 18:53:50 +00:00
future
image-types
lib Refactor app dir related flags (#41166) 2022-10-04 22:16:44 +00:00
pages fix(ts): relax AppProps to not require generic (#41264) 2022-10-07 14:59:32 -07:00
server Fix CSS imports tree-shaking (#41357) 2022-10-12 13:41:19 +00:00
shared/lib Ensure RSC paths are normalized in minimal mode (#41348) 2022-10-12 07:17:17 +00:00
telemetry
trace
types Handle error overlay for new router (#41325) 2022-10-11 16:11:57 +02:00
amp.d.ts
amp.js
app.d.ts
app.js
babel.d.ts
babel.js
client.d.ts
client.js
config.d.ts
config.js
constants.d.ts
constants.js
document.d.ts
document.js
dynamic.d.ts
dynamic.js
error.d.ts
error.js
head.d.ts
head.js
image.d.ts
image.js
index.d.ts
jest.d.ts
jest.js
license.md
link.d.ts
link.js
package.json v12.3.2-canary.25 2022-10-11 14:28:59 -07:00
README.md
router.d.ts
router.js
script.d.ts
script.js
server.d.ts
server.js
taskfile-ncc.js
taskfile-swc.js Client component directive: use client (#41333) 2022-10-11 10:26:45 -07:00
taskfile.js Handle error overlay for new router (#41325) 2022-10-11 16:11:57 +02:00
tsconfig.json

Next.js

Getting Started

Visit https://nextjs.org/learn to get started with Next.js.

Documentation

Visit https://nextjs.org/docs to view the full documentation.

Who is using Next.js?

Next.js is used by the world's leading companies. Check out the Next.js Showcase to learn more.

Community

The Next.js community can be found on GitHub Discussions, where you can ask questions, voice ideas, and share your projects.

To chat with other community members you can join the Next.js Discord.

Our Code of Conduct applies to all Next.js community channels.

Contributing

Please see our contributing.md.

Good First Issues

We have a list of good first issues that contain bugs that have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.

Authors

Security

If you believe you have found a security vulnerability in Next.js, we encourage you to responsibly disclose this and not open a public issue. We will investigate all legitimate reports. Email security@vercel.com to disclose any security vulnerabilities.

https://vercel.com/security