- 26 Oct, 2021 17 commits
-
-
jj@jjsweb.site authored
-
jj@jjsweb.site authored
-
Tim Neutkens authored
-
Lee Robinson authored
Co-authored-by:Steven <steven@ceriously.com>
-
Javi Velasco authored
Co-authored-by:
JJ Kasper <jj@jjsweb.site> Co-authored-by:
Steven <steven@ceriously.com>
-
JJ Kasper authored
This ensures we remove null bytes from the resolved path as it isn't valid when using `path`/`fs`. Additional tests have been added to ensure this is handled properly. ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/issues/30298
-
Maia Teegarden authored
Co-authored-by:Tim Neutkens <timneutkens@me.com>
-
JJ Kasper authored
* Move outputFileTracing config up * remove old nftTracing config * remove old config Co-authored-by:Steven <steven@ceriously.com>
-
Steven authored
-
Steven authored
-
JJ Kasper authored
-
Maia Teegarden authored
-
Maia Teegarden authored
-
Maia Teegarden authored
-
Maia Teegarden authored
* Publish more swc targets * Remove prebuilt binaries * Use correct path for caching * Build next-swc binaries * Remove unused job dependency
-
Kara authored
In #29010, we started throwing an error if the res was mutated after getServerSideProps() returned. This was to support classic streaming, where it would be possible to accidentally mutate the response headers after they were already sent. However, this change also caught [a few non-streaming cases](https://github.com/vercel/next.js/pull/29010#issuecomment-943482743) that we don't want to break. As such, with this change, we only throw the error if res is mutated after gSSP returns *and* you've opted into using classic streaming. Otherwise, we will only add a warning to the console.
-
jj@jjsweb.site authored
-
- 25 Oct, 2021 21 commits
-
-
JJ Kasper authored
-
Javi Velasco authored
Co-authored-by:Steven <steven@ceriously.com>
-
Steven authored
-
Kara authored
This change addresses some feedback that some users don't realize that the `priority` attribute exists and is critical for managing LCP when using the next/image component. It adds a dedicated section to the Image Optimization doc that explains how and when to use the attribute. Fixes #29624 ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
Tim Neutkens authored
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have 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 helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint`
-
jj@jjsweb.site authored
-
matamatanot authored
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have 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 helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint`
-
JJ Kasper authored
Co-authored-by:
Steven <steven@ceriously.com> Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
JJ Kasper authored
-
Tobias Koppers authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Tim Neutkens authored
## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have 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 helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint`
-
Tim Neutkens authored
Co-authored-by:
Lee Robinson <me@leerob.io> Co-authored-by:
Steven <steven@ceriously.com>
-
Tobias Koppers authored
-
JJ Kasper authored
-
Donny/강동윤 authored
Co-authored-by:
kdy1 <kdy1@users.noreply.github.com> Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> Co-authored-by:
Tim Neutkens <timneutkens@me.com>
-
Tim Neutkens authored
-
Tim Neutkens authored
-
Tobias Koppers authored
-
JJ Kasper authored
-
jj@jjsweb.site authored
-
Tim Neutkens authored
* Ensure isServer is true when compiling middleware * Update packages/next/build/webpack-config.ts Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com> * Update packages/next/build/webpack-config.ts Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by:
Tobias Koppers <tobias.koppers@googlemail.com>
-
- 24 Oct, 2021 2 commits
-
-
Tobias Koppers authored
resolve absolute URLs in CSS when using urlImports remove `[path]` from static static image output path replace file-loader with asset module, remove file-loader
-
jj@jjsweb.site authored
-