- 24 Jun, 2021 1 commit
-
-
JJ Kasper authored
-
- 23 Jun, 2021 6 commits
-
-
Steven authored
In PR #26281, we solved one use case but broke another. This PR will allow the user to [override the built-in loader](https://github.com/vercel/next.js/pull/26281#issuecomment-866251944) via custom webpack config.
-
JJ Kasper authored
* Add note about adding additional types * Update to bold edit also * Apply suggestions from code review Co-authored-by:Steven <steven@ceriously.com>
-
destruc7i0n authored
Currently, there is only a `hashChangeStart` and subsequent `hashChangeComplete` event and no props update (which would be used to get translations, etc.). Happy for any feedback fixes #23467 ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
Lee Robinson authored
Closes https://github.com/vercel/next.js/issues/12019 with a better example of proper SSR caching.
-
JJ Kasper authored
This ensures we don't recommend editing the `next-env` file since we need to be able to tweak it to accept future types we add in Next.js ## Documentation / Examples - [x] Make sure the linting passes Closes: https://github.com/vercel/next.js/issues/26533
-
Vitaly Baev authored
## Documentation / Examples - [x] Make sure the linting passes According to new requirements in `package.json` minimum Node.js version for now is 12.0
-
- 22 Jun, 2021 12 commits
-
-
Alex Castle authored
fixes #21549 Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
JJ Kasper authored
-
JJ Kasper authored
-
JJ Kasper authored
-
Brandon Bayer authored
This strongly types `Router.events.on` and `Router.events.off`. Previously the event type was `string` but now it's `'routeChangeStart' | 'beforeHistoryChange' | 'routeChangeComplete' | 'routeChangeError' | 'hashChangeStart' | 'hashChangeComplete'` ## Bug - ~[ ] Related issues linked using `fixes #number`~ - [x] Integration tests added Closes #25679 Closes #23753 Closes #15497
-
JJ Kasper authored
-
JJ Kasper authored
Closes: https://github.com/vercel/next.js/issues/24991 ## Documentation / Examples - [x] Make sure the linting passes
-
JJ Kasper authored
* Update to only add image import types when enabled * add type check to test
-
Rob Vermeer authored
* bug: Fix domain locales not available on client * Add test case * update tests Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Peter Mekhaeil authored
This Pull Request adds [Alex](https://alexjs.com/) to our documentation. It catches insensitive, inconsiderate writing. The original PR (https://github.com/vercel/next.js/pull/25821) is too large so I have decided to break it down into smaller PRs. This PR is the first part. Then I will continue to add the rest of the documentation in smaller PRs. ## More Information on Alex: https://alexjs.com/ https://github.com/get-alex/alex ## Documentation / Examples - [x] Make sure the linting passes
-
Jiachi Liu authored
Fixes #22329 ## Bug - [x] Related issues linked using fixes #22329 - [x] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
Sam Robbins authored
Without `module.exports`, the provided code won't work if just pasted into `next.config.js` ## Documentation / Examples - [x] Make sure the linting passes
-
- 21 Jun, 2021 4 commits
-
-
Vitaly Baev authored
## Documentation / Examples - [x] Make sure the linting passes Fixes #26436 As mention in #25854 `with-webassembly` example doesn't work anymore after switching to webpack 5. This PR adds webpack experimental configuration.
-
Tim Neutkens authored
-
Tim Neutkens authored
-
JJ Kasper authored
This adds a note to the router doc explaining that page state is not reset by default when updating the URL but staying on the same page as this has come up in a few issues. ## Documentation / Examples - [x] Make sure the linting passes x-ref: https://github.com/vercel/next.js/issues/26270
-
- 20 Jun, 2021 4 commits
-
-
Lee Robinson authored
Due to the period at the end of this sentence, when clicking on the link it would 404. This PR simply removes the period from the message.
-
Lee Robinson authored
-
Guilherme Araújo authored
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [x] Make sure the linting passes
-
Akash Patel authored
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
- 18 Jun, 2021 10 commits
-
-
Lee Robinson authored
* Improve the `next/script` documentation. * lint-fix Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Paco authored
-
JJ Kasper authored
-
Lee Robinson authored
-
Tim Neutkens authored
Updates the hotUpdateChunk to include `[runtime]` for web workers support. Fixes #26152 Fixes #19865 Fixes #26144 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added ## 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. ## Documentation / Examples - [ ] Make sure the linting passes
-
Joe Bell authored
* docs: extend disclaimer for dynamic image imports * docs: extend guidance on blurDataURL * Update docs/api-reference/next/image.md Co-authored-by:
Steven <steven@ceriously.com> Co-authored-by:
Tim Neutkens <tim@timneutkens.nl>
-
Luke Ingalls authored
-
Houssein Djirdeh authored
-
JJ Kasper authored
-
Steven authored
This PR does a couple things: 1. Omit svg static imports if the user has defined custom webpack config with svg rule 2. Change TS type to `any` for svg imports to avoid conflicts with other plugins The idea is that some users want to use `next/image` with static imports for most image types but not for svg and instead inline those images with a plugin. - Fixes #25950 - Fixes #26130 - Fixes #26176 - Fixes #26196 - Fixes #26067 ## Bug - [x] Related issues linked using Fixes #26130 - [x] Integration tests added
-
- 17 Jun, 2021 3 commits
-
-
Gerald Monaco authored
Also logs a message when defaulting, and a warning when using a prerelease build of `react-dom` (e.g. the React 18 alpha) which are not officially supported. Note: I've done this in `webpack-config.ts` instead of the Next.js config, as we don't actually want you to be able to opt-out *without* downgrading back to React 17, and so it ought to be entirely removed from the config eventually.
-
JJ Kasper authored
* Update to latest TypeScript version and de-dupe versions * Update version test
-
Taehun Jeong authored
## Bug - [x] Related issues linked using `fixes #26135 ` - [x] Integration tests added fixes #26135 ## 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 #26135 ` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. ## Documentation / Examples - [ ] Make sure the linting passes
-