Sam Ko and GitHub
151d07e148
examples: update app-dir-i18n-routing to v15 ( #72636 )
...
## Why?
The example `app-dir-i18n-routing` needs to be updated to v15.
## How?
Run the `next-async-request-api` codemod:
```
pnpm dlx @next/codemod@latest next-async-request-api .
```
- Fixes https://github.com/vercel/next.js/issues/72630
2024-11-12 14:29:36 -08:00
Vercel Release Bot and GitHub
18b357854b
Upgrade React from 66855b96-20241106 to 5c56b873-20241107 ( #72469 )
2024-11-11 10:29:01 +00:00
b005bdce38
example: add more files to playwright .gitignore ( #72447 )
...
## Description
[create-playwright](https://github.com/microsoft/create-playwright )
makes the below special `.gitignore` file.
```txt
node_modules/
/test-results/
/playwright-report/
/blob-report/
/playwright/.cache/
```
It's good to add these files to .gitignore for convinience.
### Adding or Updating Examples
- [x] The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- [x] Make sure the linting passes by running `pnpm build && pnpm lint`.
See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
Co-authored-by: JJ Kasper <[email protected]
2024-11-08 19:27:48 +00:00
a9492ffa12
chore: update typescript document path ( #72482 )
...
## Description
At #72178 ,
[TypeScript](https://nextjs.org/docs/app/api-reference/config/typescript )
docs was moved.
So update the old URLs.
### Improving Documentation
- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
---------
Co-authored-by: Zack Tanner <[email protected]
2024-11-07 14:42:24 -08:00
1c22d142e0
chore: delete api-routes example completely ( #72437 )
...
## Description
At #68771 ,
[`api-routes`](https://github.com/vercel/next.js/tree/canary/examples/api-routes )
example was renamed
[`route-handlers`](https://github.com/vercel/next.js/tree/canary/examples/route-handlers ).
However,
[`.gitignore`](https://github.com/vercel/next.js/blob/canary/examples/api-routes/.gitignore )
wasn't deleted and a new
[`.gitignore`](https://github.com/vercel/next.js/blob/canary/examples/route-handlers/.gitignore )
file isn't updated.
In addition, some `api-routes` names exist in the other place.
That's why I update those.
### Improving Documentation
- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
Co-authored-by: JJ Kasper <[email protected]
2024-11-07 20:00:45 +00:00
d8c1875800
chore: add syntax parser directive to Dockerfile ( #72380 )
...
## What?
Add [`syntax`](https://docs.docker.com/reference/dockerfile/#syntax )
parser directive to the first line of the
[Dockerfile](https://docs.docker.com/reference/dockerfile/ ).
## Why?
To declare the Dockerfile syntax version to use for the build.
If unspecified, [BuildKit](https://docs.docker.com/build/buildkit/ ) uses
a bundled version of the Dockerfile frontend.
## How?
Append `# syntax=docker.io/docker/dockerfile:1` to the top of the
[Dockerfile](https://docs.docker.com/reference/dockerfile/ ).
Co-authored-by: JJ Kasper <[email protected]
2024-11-06 23:22:46 +00:00
Vercel Release Bot and GitHub
8278fcc6f1
Upgrade React from 7c8e5e7a-20241101 to 66855b96-20241106 ( #72415 )
2024-11-06 17:12:33 +00:00
Jiwon Choi and GitHub
570ed9674a
examples: check-examples.sh considers src/app as Pages Router ( #72332 )
2024-11-06 00:49:05 +09:00
Jiwon Choi and GitHub
cf8273ba99
examples: pin react rc version for blog-starter ( #72334 )
...
Fails while deploying: `npm` peerDeps error.
x-ref: [slack
thread](https://vercel.slack.com/archives/C07UQ745AFQ/p1730812055364329?thread_ts=1730810142.903609&cid=C07UQ745AFQ )
2024-11-06 00:13:19 +09:00
Jiwon Choi and GitHub
80dbb1b04f
examples: blog-starter used params without await ( #72327 )
...
### Why?
Example `blog-starter` was using `params` without awaiting.
2024-11-05 21:57:09 +09:00
Balázs Orbán and GitHub
0ffc5f7b59
Revert "docs: change NextAuth.js to Auth.js" ( #72257 )
2024-11-04 11:42:54 +00:00
Vercel Release Bot and GitHub
c479c04e3e
Upgrade React from 603e6108-20241029 to 7c8e5e7a-20241101 ( #72199 )
2024-11-03 19:11:20 +01:00
94eca4bb56
docs: change NextAuth.js to Auth.js ( #72201 )
...
## Summary
[`NextAuth.js`](https://next-auth.js.org/ ) is becoming
[`Auth.js`](https://authjs.dev/ )!
Then update new documentation link.
### Improving Documentation
- [x] Run `pnpm prettier-fix` to fix formatting issues before opening
the PR.
- [x] Read the Docs Contribution Guide to ensure your contribution
follows the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
Co-authored-by: Zack Tanner <[email protected]
2024-11-03 16:05:40 +00:00
AliReza Bahrani and GitHub
39c4cf9ab5
examples: Add .npmrc to Dockerfile to support custom npm configs ( #72132 )
...
### Description:
This PR continues the work started in
[#72064 ](https://github.com/vercel/next.js/pull/72064 ) (already merged)
by updating the Dockerfiles in the `examples` folder to include the
`.npmrc` file in the dependency copy command.
### Original Command:
```dockerfile
# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
```
### Updated Command:
```dockerfile
# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
```
### Reason for Change:
Including `.npmrc` allows for custom npm configurations, such as
`legacy-peer-deps=true`. Without this option, some installations can
fail due to unresolved peer dependencies, particularly for projects with
older dependencies.
This update ensures that any additional configurations specified in
`.npmrc` are applied during installation, improving Docker build
consistency and stability for projects with custom npm requirements.
### Diff:
```diff
- COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
+ COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc* ./
```
2024-11-01 10:46:01 -07:00
Jam Balaya and GitHub
00f9884d56
examples: change --turbo to --turbopack ( #72125 )
2024-10-31 14:55:55 +01:00
Vercel Release Bot and GitHub
e3c6b44b1a
Upgrade React from 02c0e824-20241028 to 603e6108-20241029 ( #72089 )
2024-10-30 17:51:13 +01:00
d85e2ae05e
Add .npmrc file to Dockerfile for custom npm configurations ( #72064 )
...
### Description:
This PR updates the Dockerfile in the `examples/with-docker` folder to
include the `.npmrc` file in the dependency copy command.
### Original Command:
```dockerfile
# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
```
### Updated Command:
```dockerfile
# Install dependencies based on the preferred package manager
COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc ./
```
### Reason for Change:
Including `.npmrc` allows for custom npm configurations, such as
`legacy-peer-deps=true`. Without this option, some installations can
fail due to unresolved peer dependencies, particularly for projects with
older dependencies.
This update ensures that any additional configurations specified in
`.npmrc` are applied during installation, improving Docker build
consistency and stability for projects with custom npm requirements.
### Diff:
```diff
- COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./
+ COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* .npmrc ./
```
---------
Co-authored-by: JJ Kasper <[email protected]
2024-10-30 15:57:09 +00:00
41b5e63581
examples: add missing project name ( #72015 )
...
## Summary
According to [Adding
examples](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md ),
`auth-app` project name is needed.
### Adding or Updating Examples
- [x] The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- [x] Make sure the linting passes by running `pnpm build && pnpm lint`.
See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
Co-authored-by: JJ Kasper <[email protected]
2024-10-29 18:46:02 -07:00
Jam Balaya and GitHub
4353c8f8ef
example: typo yarn → next ( #72018 )
...
## Summary
The old analyze command use `yarn build`.
This happens an error with node, pnpm and bun.
### Adding or Updating Examples
- [x] The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- [x] Make sure the linting passes by running `pnpm build && pnpm lint`.
See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
2024-10-30 01:39:59 +00:00
8f0d5834fe
examples: replace the all docker-compose.yml with compose.yaml ( #71006 )
...
# Summary
Rename docker compose file to `compose.yaml`.
Update docker compose command.
## Description
According to [official
manuals](https://docs.docker.com/compose/intro/compose-application-model/#the-compose-file ),
> The default path for a Compose file is `compose.yaml` (preferred) or
`compose.yml` that is placed in the working directory. Compose also
supports `docker-compose.yaml` and `docker-compose.yml` for backwards
compatibility of earlier versions. If both files exist, Compose prefers
the canonical `compose.yaml`.
### Adding or Updating Examples
- [x] The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- [x] Make sure the linting passes by running `pnpm build && pnpm lint`.
See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
x-ref: [The Compose
file](https://docs.docker.com/compose/intro/compose-application-model/#the-compose-file )
x-ref: [docker-compose vs docker
compose](https://docs.docker.com/compose/releases/migrate/#docker-compose-vs-docker-compose )
Co-authored-by: JJ Kasper <[email protected]
2024-10-29 15:29:10 -07:00
5a4d159846
examples: rename dbConnect.ts at comment in payload example ( #71685 )
...
## Summary
Just change `dbConnect.js` to `dbConnect.ts` for correct path.
### Adding or Updating Examples
- [x] The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- [x] Make sure the linting passes by running `pnpm build && pnpm lint`.
See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
Co-authored-by: JJ Kasper <[email protected]
2024-10-29 19:44:50 +00:00
420ba68638
Fix deployment and auth links to align with Next.js App Router ( #71589 )
...
This PR addresses the following fixes:
**fix: update the deployment link to Next.js App Router**
- Updated the deployment link to point to the Next.js App Router instead
of the Pages Router since the example now has the pages router
**fix: App Router deployment link for app-dir-i18n-routing example**
- Corrected the deployment link for the app-dir-i18n-routing example to
match the App Router deployment structure.
**fix: Stytch auth link updated to Next.js**
- Updated the Stytch authentication link to work with the Next.js setup,
previous link was pointed to Javascript example.
---------
Co-authored-by: JJ Kasper <[email protected]
2024-10-29 19:40:33 +00:00
88238fb5a8
chore: delete redundant blank spaces in examples ( #71239 )
...
## 📚 Fixed some typos
Hello, while reviewing the source code in `examples` directory, I found
some unnecessary blank spaces. So I fixed them.
Co-authored-by: JJ Kasper <[email protected]
2024-10-29 19:29:54 +00:00
7851e1865e
example: fix typo _app_.tsx → _app.tsx ( #71686 )
...
## Wrong
https://github.com/vercel/next.js/blob/canary/examples/with-segment-analytics-pages-router/pages/_app_.tsx
## Correct
https://github.com/vercel/next.js/blob/canary/examples/with-segment-analytics-pages-router/pages/_app.tsx
### Adding or Updating Examples
- [x] The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- [x] Make sure the linting passes by running `pnpm build && pnpm lint`.
See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
Co-authored-by: JJ Kasper <[email protected]
2024-10-29 19:11:05 +00:00
Vercel Release Bot and GitHub
8b65ec1b84
Upgrade React from 1631855f-20241023 to 02c0e824-20241028 ( #71979 )
2024-10-29 00:37:10 +01:00
Sergey Rubanov and GitHub
35cd36e9d5
experimental.instrumentationHook is not necessary anymore ( #71808 )
2024-10-26 22:53:40 +02:00
Vercel Release Bot and GitHub
4ae3fc3e35
Upgrade React from 28668d39-20241023 to 1631855f-20241023 ( #71769 )
...
**breaking change for canary users: Bumps peer dependency of React from
`19.0.0-rc-28668d39-20241023` to `19.0.0-rc-1631855f-20241023`**
[diff
facebook/[email protected] ](https://github.com/facebook/react/compare/28668d39...1631855f )
<details>
<summary>React upstream changes</summary>
- https://github.com/facebook/react/pull/31340
</details>
2024-10-23 23:57:26 +00:00
Vercel Release Bot and GitHub
c464672dde
Upgrade React from 45804af1-20241021 to 28668d39-20241023 ( #71745 )
2024-10-23 21:41:46 +02:00
Sebastian "Sebbie" Silbermann and GitHub
babc6a0242
Update React from 69d4b800-20241021 to 45804af1-20241021 ( #71718 )
2024-10-23 16:55:39 +00:00
Cody Olsen and GitHub
cfd816ddb8
Update Sanity example to next v15 ( #71640 )
2024-10-22 22:14:43 +02:00
703d276ecb
examples: Update with-supabase to be compatible with Nextjs 15 ( #71631 )
...
Co-authored-by: Lee Robinson <[email protected]
2024-10-22 13:10:04 -05:00
Vercel Release Bot and GitHub
8a905cf0cb
Upgrade React from 65a56d0e-20241020 to 69d4b800-20241021 ( #71568 )
...
**breaking change for canary users: Bumps peer dependency of React from
`19.0.0-rc-65a56d0e-20241020` to `19.0.0-rc-69d4b800-20241021`**
[diff
facebook/[email protected] ](https://github.com/facebook/react/compare/65a56d0e...69d4b800 )
<details>
<summary>React upstream changes</summary>
- https://github.com/facebook/react/pull/31313
</details>
2024-10-22 00:04:01 +02:00
Sebastian Markbåge and GitHub
164723263b
Update React (again) ( #71528 )
2024-10-20 03:31:42 -04:00
Sebastian Markbåge and GitHub
eb02b78afe
Update React to bf7e210c ( #71524 )
2024-10-19 22:37:52 -07:00
Vercel Release Bot and GitHub
3ff9b8b9d8
Upgrade React from 77b637d6-20241016 to bf7e210c-20241017 ( #71436 )
2024-10-18 10:23:31 +00:00
4d8442af58
chore(examples): updated the example of with-styled-jsx to utilize the App Route ( #71290 )
...
This PR updates the with-styled-jsx example to use the App Router. Here
are the changes that have been made:
- Renamed the `pages` folder to the `app` folder.
- Added the `layout.tsx` file as part of the App Router.
- Updated the `package.json` file.
The following actions were performed as part of this PR:
- Ran `pnpm prettier-check` with no issues found.
- Executed the `pnpm check-examples` script.
CC: @samcx
---------
Co-authored-by: samcx <[email protected]
2024-10-17 19:25:15 +00:00
a1dbc073e4
chore(examples): updated the example of with-goober to utlize the App router ( #71349 )
...
This PR updates the `with-goober` example to use the App Router. Here
are the changes that have been made:
- Renamed the `pages` folder to the` app` folder.
- Converted the `index.tsx` to ` page.tsx ` file as part of the App
Router.
- Created a new `layout.tsx` file in the app directory.
- Merged functionality from both `_app.tsx` and `_document.tsx` into
`layout.tsx`:
- Goober setup from `_app.tsx`
- CSS extraction and injection from `_document.tsx`
- Updated the `package.json` file.
The following actions were performed as part of this PR:
- Ran `pnpm prettier-check` with no issues found.
- Executed the `pnpm check-examples` script.
**CC:** @samcx
---------
Co-authored-by: samcx <[email protected]
2024-10-17 17:57:06 +00:00
cad01db9d2
Upgrade React from cd22717c-20241013 to 77b637d6-20241016 ( #71391 )
...
Co-authored-by: eps1lon <[email protected]
2024-10-17 09:48:02 +00:00
300bfe52f4
[BREAKING] Support ESLint v9 in plugin, config and next lint ( #71218 )
...
> [!WARNING]
> **Breaking Change:** Now uses `[email protected] ` which
has a new violation disallowing Component names starting with anything
but an uppercase letter. See
https://github.com/facebook/react/releases/tag/eslint-plugin-react-hooks%405.0.0
for more details.
Adds support of ESLint v9 to `eslint-plugin-next`, `eslint-config-next`
and `next lint`.
Does not require using the new flat config format. `next lint` will
automatically ensure the old config format can be used.
### Why?
As `eslint-plugin-react-hooks` has been updated for ESLint v9 support
and is a helpful package for Next v15 upgrade, unblock the restrictions
to upgrade to ESLint v9.
Also, ESLint v8 is [End of
Life](https://eslint.org/blog/2024/09/eslint-v8-eol-version-support/#:~:text=ESLint%20v8.-,x%20end%20of%20life%20is%20October%205%2C%202024,x%20on%20October%205%2C%202024 .)
support since Oct 5th, so is good to unblock v9 now.
Plugins bumped:
- [x]
[@rushstack/eslint-patch](https://github.com/microsoft/rushstack/pull/4719 )
([v1.10.3](https://www.npmjs.com/package/@rushstack/eslint-patch/v/1.10.3?activeTab=versions )
no release post, confirmed on NPM)
- [x]
[@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/pull/9002 )
([v8.0.0](https://github.com/typescript-eslint/typescript-eslint/pull/9002#issuecomment-2106424400 ))
- [x]
[eslint-plugin-import](https://github.com/import-js/eslint-plugin-import/pull/2996 )
([v2.31.0](https://github.com/import-js/eslint-plugin-import/releases/tag/v2.31.0 ))
- [x]
[eslint-plugin-jsx-a11y](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/pull/1009 )
([v6.10.0](https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/releases/tag/v6.10.0 ))
- [x]
[eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react/pull/3759 )
([v7.35.0](https://github.com/jsx-eslint/eslint-plugin-react/releases/tag/v7.35.0 ))
- [x]
[eslint-plugin-react-hooks](https://github.com/facebook/react/pull/28773 )
([v5.0.0](https://github.com/facebook/react/releases/tag/eslint-plugin-react-hooks%405.0.0 ))
We have to switch to ESLint v9 in our repo due to a pnpm bug where it
automatically uses ESLint v9 even though we only installed it via
`eslint-v9: npm:[email protected] `. This is a pnpm bug that wouldn't happen
with Yarn v1, v4 nor NPM.
Closes https://github.com/vercel/next.js/issues/64409
Closes https://github.com/vercel/next.js/issues/64114
Closes https://github.com/vercel/next.js/issues/64453
Closes NEXT-3293
---------
Co-authored-by: Sebastian "Sebbie" Silbermann <[email protected]
2024-10-15 03:57:55 +09:00
Vercel Release Bot and GitHub
69efa49c8e
Upgrade React from 70fb1363-20241010 to cd22717c-20241013 ( #71223 )
2024-10-13 19:37:00 +00:00
465214b21f
docs(typo): fix typo in cms-sanity example README.md ( #71211 )
...
Fixing typos for the `cms-sanity` example
[README.md](https://github.com/vercel/next.js/blob/canary/examples/cms-sanity/README.md ):
`envionment` > `environment`
`alredy` > `already`
Thanks!
Co-authored-by: JJ Kasper <[email protected]
2024-10-13 15:26:26 +00:00
2f7a48fa4d
Upgrade React from 2d16326d-20240930 to 70fb1363-20241010 ( #71118 )
...
Co-authored-by: eps1lon <[email protected]
2024-10-11 17:03:27 +00:00
89c6e205e9
chore(examples):updated the example of with-stitches to utlize the App router ( #71007 )
...
This PR updates the with-stitches example to use the App Router. Here
are the changes that have been made:
- Renamed the `pages` folder to the` app` folder.
- Added the ` layout.tsx ` file as part of the App Router.
- Converted the `index.tsx` to ` page.tsx ` file as part of the App
Router.
- Updated the `package.json` file.
- Moved the `components` folder inside `app` folder.
The following actions were performed as part of this PR:
- Ran `pnpm prettier-check` with no issues found.
- Executed the `pnpm check-examples` script.
**CC:** @samcx
---------
Co-authored-by: samcx <[email protected]
2024-10-09 20:56:07 -07:00
78b73f03e1
replace all 'athName' with 'athname' for consistency ( #70690 )
...
### What?
Consistently casing of pathname throughout the code-base. It is a simple
search and replace of all the ocuences 'athName' to 'athname'.
### Why?
I believe that the usage of the casing [pP]athName is likely a mistake,
as it is usually typed [pP]athname in the rest of the repo.
I think a case sensitive search replace from 'athName' to 'athname'
would be a small thing, and prevent this from growing.
### How?
I searched for pathname in the repo, and found a huge amount of hits.
Searching for 'athName' only returned a few.
The usePathname hook was the reason I came across this inconsistency. We
had the inconsistency in our own Next.js project, ie. `const pathName =
usePathname()`, and I noticed that when searching inside my project with
cases-sensitivity I found two hits of 'pathName' inside the
documentation for LoadableManifest.
This lead me to fork the repo and search, and then I found a few more
cases.
In each file I did a search for conflicts: if for example pathname was
already defined, it would be considered breaking if I changed a pathName
to pathname.
I could not find any cases where the variable was defined twice with the
same casing, so I believe this PR is safe.
I guess the test coverage/pipeline will tell us if this change is
breaking? If not I don't think I would be able to contribute that much
further in the time of writing.
Co-authored-by: JJ Kasper <[email protected]
2024-10-08 15:11:59 +00:00
7474f10c96
chore(examples): updated the example of with-styled-components ( #70796 )
...
This PR updates the with-styled-components example to use the App
Router. Here are the changes that have been made:
- Renamed the `pages` folder to the `app` folder.
- Updated the routing for `/` & `/about` files to align with the App
Router.
- Added the `layout.tsx` file as part of the App Router.
- Updated the `package.json` file.
The following actions were performed as part of this PR:
- Ran `pnpm prettier-check` with no issues found.
- Executed the `pnpm check-examples` script.
CC: @samcx
---------
Co-authored-by: samcx <[email protected]
2024-10-04 11:14:57 -07:00
eecf90c09a
updated the environment variables examples to utilize the App router ( #70392 )
...
This PR updates the `environment-variables` example to use the App
Router. Here are the changes that have been made:
- Created an `app` folder and added `page.tsx` file.
- Added `layout.tsx` file
- Updated the `readme.md` file.
- Updated the `package.json` file.
cc : @samcx
---------
Co-authored-by: samcx <[email protected]
2024-09-30 23:16:58 -07:00
Vercel Release Bot and GitHub
95820c4066
Upgrade React from 3edc000d-20240926 to 2d16326d-20240930 ( #70629 )
2024-10-01 01:08:12 +02:00
1facc7fa92
[Multi-Zones] Update example and documentation with most recent practices for Multi-Zones ( #70565 )
...
<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:
## For Contributors
### Improving Documentation
- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide
### Adding or Updating Examples
- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md
### Fixing a bug
- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
### Adding a feature
- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas )
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs )
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md
## For Maintainers
- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change
### What?
### Why?
### How?
Closes NEXT-
Fixes #
-->
---------
Co-authored-by: JJ Kasper <[email protected]
2024-09-28 21:07:15 +00:00
179f2e461c
Fix Stackblitz preview link on with-opentelemetry example ( #70543 )
...
Co-authored-by: JJ Kasper <[email protected]
2024-09-28 20:48:23 +00:00
af8af5ea7e
Upgrade React from 778e1ed2-20240926 to 3edc000d-20240926 ( #70560 )
...
**breaking change for canary users: Bumps peer dependency of React from
`19.0.0-rc-778e1ed2-20240926` to `19.0.0-rc-3edc000d-20240926`**
[diff
facebook/[email protected] ](https://github.com/facebook/react/compare/778e1ed2...3edc000d )
<details>
<summary>React upstream changes</summary>
- https://github.com/facebook/react/pull/31078
- https://github.com/facebook/react/pull/31083
- https://github.com/facebook/react/pull/31079
- https://github.com/facebook/react/pull/31080
- https://github.com/facebook/react/pull/31076
- https://github.com/facebook/react/pull/31021
- https://github.com/facebook/react/pull/31069
- https://github.com/facebook/react/pull/31074
- https://github.com/facebook/react/pull/31073
- https://github.com/facebook/react/pull/31047
- https://github.com/facebook/react/pull/31046
- https://github.com/facebook/react/pull/31045
- https://github.com/facebook/react/pull/31072
- https://github.com/facebook/react/pull/30980
- https://github.com/facebook/react/pull/30463
- https://github.com/facebook/react/pull/30694
- https://github.com/facebook/react/pull/31039
- https://github.com/facebook/react/pull/31048
- https://github.com/facebook/react/pull/31068
</details>
---------
Co-authored-by: Josh Story <[email protected]
2024-09-27 13:08:06 -07:00
