Improve TypeScript plugin error when the configuration is not statically analyzable (#42062)
As per https://github.com/vercel/next.js/issues/41951#issuecomment-1294199692, this PR improves the TS plugin error message when a non-literal configuration is used: <img width="902" alt="CleanShot 2022-10-28 at 07 36 31@2x" src="https://user-images.githubusercontent.com/3676859/198650771-026a0430-d5bc-4826-9aef-b1bfb7947c6f.png"> Also a bug is fixed so string template literals (``const revalidate = `auto`;``) will no longer result in an error. ## 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 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)
Showing
Please
register
or
sign in
to comment