8ded79728e
Follow up to #43903, this PR adds named slots to the generated typings, and provides better error messages for `next build`. For example, a layout can have `test` as a prop because it has `@test` co-located. But `invalid` is not a possible prop here:  And here's the error when running `next build`: <img width="651" alt="CleanShot 2022-12-09 at 21 21 11@2x" src="https://user-images.githubusercontent.com/3676859/206789969-8bbd75bd-e7e3-4109-9e0d-d5f8f9a4bbb5.png"> ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/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` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) 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`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) |
||
|---|---|---|
| .. | ||
| analysis | ||
| babel | ||
| jest | ||
| output | ||
| polyfills | ||
| swc | ||
| webpack | ||
| compiler.ts | ||
| cssnano-simple.js | ||
| entries.ts | ||
| generate-build-id.ts | ||
| index.ts | ||
| is-writeable.ts | ||
| load-jsconfig.ts | ||
| spinner.ts | ||
| utils.ts | ||
| webpack-config.ts | ||
| worker.ts | ||
| write-build-id.ts | ||
