- 28 Oct, 2021 11 commits
-
-
Tobias Koppers authored
-
Tobias Koppers authored
This reverts commit 387d6564.
-
Donny/강동윤 authored
-
Donny/강동윤 authored
Co-authored-by:kdy1 <kdy1@users.noreply.github.com>
-
Kai Malcolm authored
This PR adds documentation on how to debug through VS Code on Windows. Closes #30231 ## Documentation / Examples - [x] Make sure the linting passes
-
Donny/강동윤 authored
Co-authored-by:kdy1 <kdy1@users.noreply.github.com>
-
JJ Kasper authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Tim Neutkens authored
-
JJ Kasper authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Lucas Vazquez authored
Several examples at https://nextjs.org/docs/api-reference/next.config.js/headers have a comma at the end of the returns, which makes them invalid examples.
-
Maia Teegarden authored
* Fix issue with placeholder followed by numbers * Build next-swc binaries
-
- 27 Oct, 2021 26 commits
-
-
Balázs Orbán authored
I changed the order of `NextRequest` and `NextFetchEvent` as they are presented in the function signature. There also seemed to be some issues with the heading levels. Also, `NextResponse` is a documented API, but the example code uses `Response`. I wasn't sure if this was a mistake in the docs or in the code. I noticed that other similar docs pages have a collapsible `Examples` section at their top: - https://nextjs.org/docs/api-reference/next/image - https://nextjs.org/docs/api-reference/next/head - https://nextjs.org/docs/api-reference/next/amp Image below:  Should the Middleware docs have the same?
-
JJ Kasper authored
This ensures we don't add non-es5 code from ncc'ing Fixes: https://github.com/vercel/next.js/issues/30450 ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [x] Errors have helpful link attached, see `contributing.md`
-
JJ Kasper authored
-
JJ Kasper authored
-
JJ Kasper authored
Links the failed to load bindings error document to the new discussion here: https://github.com/vercel/next.js/discussions/30468 ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
Tim Neutkens authored
-
Tim Neutkens authored
Co-authored-by:Tobias Koppers <tobias.koppers@googlemail.com>
-
Steven authored
This warning was incorrectly displaying for the "background" use case demonstrated here: https://image-component.nextjs.gallery/background
-
Luke Howsam authored
This PR: Fixes a broken link in the testing documentation. It appears that the selector currently being used is `#test-environment-variable`. When clicked this results in the user being re-directed to the top of the environment variables page. The correct selector is: `#test-environment-variables` ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint`
-
Bruce Rodrigues authored
Just removing the duplicated use of `instead` on `next.config.js/rewrites` doc
-
Tobias Koppers authored
-
Tobias Koppers authored
-
Donny/강동윤 authored
Co-authored-by:
kdy1 <kdy1@users.noreply.github.com> Co-authored-by:
Tim Neutkens <tim@timneutkens.nl>
-
Tim Neutkens authored
-
Tobias Koppers authored
fallback to alternative external version also when it fails because of base resolve mismatch# fix resolved .mjs modules treated as external fixes #30330
-
Pierre de la Martinière authored
## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint` It's this time of the year again :^) congrats to the Next.js team for the amazing release!
-
JJ Kasper 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`
-
Donny/강동윤 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` This includes - https://github.com/swc-project/swc/pull/2530 - Strip out `declare`-d class properties properly. - https://github.com/swc-project/swc/pull/2538 - Marks method properties as a scope while renaming variables. - Fix regression of object-rest pattern handler. - Improve name mangler a bit, by marking it as a scope. - https://github.com/swc-project/swc/pull/2551 - Fix a bug of the property inlining pass which can break many react apps. There is a minor regression in the minifier due to added aliasing check. (I manually selected crates to update)
-
Tobias Koppers authored
Improve CI experience
-
JJ Kasper authored
-
Tobias Koppers authored
A tsconfig like: ``` { "extends": "..." } ``` currently fails the build if the config that is extended from has not the expected configuration (and we want to update it) Fixes: https://github.com/vercel/next.js/issues/30360 -
Oscar Busk authored
I used `create-next-app` to create a new fancy Next 12 app, ran `yarn build` and got a git diff. The tsconfig.json had a `incremental` added by next. Just running build shouldn't need I have uncommitted changes.
-
jj@jjsweb.site authored
-
jj@jjsweb.site authored
-
Steven authored
Browsers older than 2017 don't have PerformanceObserver https://caniuse.com/mdn-api_performanceobserver - Fixes https://github.com/vercel/next.js/issues/30322 - Fixes https://twitter.com/fmgordillo/status/1453037730141716492
-
- 26 Oct, 2021 3 commits
-
-
jj@jjsweb.site authored
-
Donny/강동윤 authored
We found that `.swcrc` was unintentionally loaded breaking applications as it is not tested for that yet, customization will be added at a later point in time ## 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`
-
Jiachi Liu authored
* disable concurrent test cases in short term to improve them later * remove bad alias in next.config.js
-