- 12 Jul, 2022 4 commits
-
-
Tim Neutkens authored
-
Tim Neutkens authored
Handles the case where an error is introduced which causes a Fast Refresh and then it's fixed. ## 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 `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
-
Shu Ding authored
Improve CSS modules support in server components. ## Bug - [ ] Related issues linked using `fixes #number` - [x] 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 `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) Co-authored-by:
Jiachi Liu <4800338+huozhi@users.noreply.github.com>
-
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 `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) --- - Closes #38117
-
- 11 Jul, 2022 22 commits
-
-
JJ Kasper authored
-
Balázs Orbán authored
Trying to create more consistency in our examples. ## 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 `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
-
Balázs Orbán authored
Fixes #38530 Should we consider adding a build-step to lint rules to be able to use TS/modern JS? ## 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 `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
-
Daniel Cavanagh authored
I've wasted a couple of hours trying to work out why my static build wasn't passing through the props automatically as the docs say it should Turns out it's the default app doing that and a custom app has to manually passed the props through It wasn't obvious to me to look in the custom app doc where it's mentioned, so I've added a small note to the `getStaticProps` doc about this that points to the custom app doc Co-authored-by:JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
JJ Kasper authored
## Documentation / Examples - [x] 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.md#adding-examples) x-ref: https://github.com/vercel/next.js/issues/38119
-
OJ Kwon authored
As we have disabled crash reporter for now, this PR removes feature from `default` to not to include it in `next-swc` as well. Feature itself remains so we can adjust it later by enabling it depends on the progress. ## 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 `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples) Co-authored-by:
JJ Kasper <22380829+ijjk@users.noreply.github.com>
-
Sanjaiyan Parthipan authored
Hi, I have updated some version of packages. - @swc/helper - json5 - terser - postcss - nanoid - use-sync-external-store (ReactJs pollyfill) - microbundle Updated version of #38328 _Extremely sorry if I made any mistakes :(_ Co-authored-by:Jiachi Liu <4800338+huozhi@users.noreply.github.com>
-
JJ Kasper authored
* Add dev/start timing to PR stats * get port for dev * add dep * update field names
-
OJ Kwon authored
-
Jiachi Liu authored
Fix flaky rsc test in react 17 e2e tests x-ref: https://github.com/vercel/next.js/runs/7285946966?check_suite_focus=true
-
Thiago Morales authored
# Description Hi guys! First all, thanks for provide a way to use some custom external cache resource for ISR feature. _(done here: https://github.com/vercel/next.js/pull/37258 and https://github.com/vercel/next.js/pull/37326)_ I managed to get it working by creating my custom external cache resource _(using redis)_ that implements the new `CacheHandler`. _(overriding my own `get` and `set` methods and using the FileSystemCache as fallback as well)_ I'm planning to release some kind of plugin to encapsulate and parse the client's `next.config.js` and bring an initial support for redis using this new Next.js feature. So, I really don't know if this was intentional, but I noticed that the new `incrementalCacheHandlerPath` prop wasn't passed to the `IncrementalCache` instance in `base-server`. This PR just connects the wires for this feature, and also provide the default value (`undefined`) to the relative experimental prop config. _(to avoid the warnings as shown below)_ <img width="858" alt="Screen Shot 2022-07-07 at 19 37 46" src="https://user-images.githubusercontent.com/4661217/177882897-831ade73-26ba-493a-b0cf-3de62cfd708f.png">
-
JJ Kasper authored
-
Jiachi Liu authored
* Enable css in server components * inject server css into flight * refactor and fix test * fix lint * resolve css from module deps * fix dev & prod inconsistentce, collect client css * simplify * dedupe duplicated css chunks * remove ssr link injection and css flight Co-authored-by:Shu Ding <g@shud.in>
-
Donny/강동윤 authored
This PR updates swc to https://github.com/swc-project/swc/commit/fa66ee86e5434d1b401e350d5727df378b193699
-
JJ Kasper authored
-
JJ Kasper authored
* Update CI job skipping based on related changes * add for azure too * update value * simplify docs change value * update value for swc as well
-
Tim Neutkens authored
-
Tim Neutkens authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Alex Johansson authored
Fix url of tRPC's `next-minimal-starter` ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
-
Tim Neutkens authored
* Add todo * Reload page when server component changes * Implement router.reload() that refreshes full tree
-
Cupid Valentine 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 - [x] Make sure the linting passes by running `pnpm lint` - [x] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
-
Max Proske authored
Converted API Routes example over to TypeScript to match the Contribution guidelines. ## Documentation / Examples - [X] Make sure the linting passes by running `pnpm lint` - [X] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
-
- 10 Jul, 2022 2 commits
-
-
stefanprobst authored
* chore: fix bundle-analyzer types * Add test for bundle analyzer type * fix lint Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Tim Neutkens authored
-
- 09 Jul, 2022 9 commits
-
-
OJ Kwon authored
* build(ci): enable rustls as default * test build
-
JJ Kasper authored
-
Mihai C authored
chore: update file references from README
-
Jiachi Liu authored
## Bug - [ ] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md`
-
Tim Neutkens authored
Co-authored-by:
JJ Kasper <jj@jjsweb.site> Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Jiachi Liu authored
* Migrate rsc integration tests to e2e tests * skip image test * remove image page Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Tim Neutkens authored
-
Tim Neutkens authored
-
OJ Kwon authored
Co-authored-by:Tim Neutkens <tim@timneutkens.nl>
-
- 08 Jul, 2022 3 commits
-
-
Houssein Djirdeh authored
* adds mention of inp to measuring performance docs * lint-fix Co-authored-by:JJ Kasper <jj@jjsweb.site>
-
Steven authored
## Bug - [x] Fixes #38404 - [x] Fixes #38431 - [x] Integration tests updated
-
Tim Neutkens authored
Ensures catchall parameters are passed as an array to `params` instead of as a string. ## 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 `pnpm lint` - [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
-