fda355daa2
This PR implements the process of generating strict "type guard" files, to ensure that all entrypoints have the correct export types. The type checking process happens automatically during `next build`. ## 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) Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> |
||
|---|---|---|
| .. | ||
| hot-middleware.ts | ||
| hot-reloader.ts | ||
| next-dev-server.ts | ||
| on-demand-entry-handler.ts | ||
| static-paths-worker.ts | ||