7aa5d16231
Use the automatic runtime for type checking ( #83159 )
...
Co-authored-by: Sebastian "Sebbie" Silbermann <silbermann.sebastian@gmail.com >
2025-09-02 12:35:42 +02:00
4a97643664
examples: fix readmes ( #78483 )
2025-04-23 20:48:58 -05:00
36dce2fe7e
examples: add StackBlitz preview to README.md ( #73546 )
...
### Description
Follow up #35349 .
1. Update the [example
template](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md )
with [StackBlitz](https://stackblitz.com/ ) preview
2. Add `preview live with StackBlitz` to the examples
3. Remove the below old StackBlitz preview section from the examples
```md
## Preview
Preview the example live on [StackBlitz](http://stackblitz.com/ ):
[](https://stackblitz.com/github/vercel/next.js/tree/canary/examples/active-class-name )
```
CC: @samcx
### 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
### 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
2025-01-14 05:24:51 +00:00
9d371bfa82
examples: unify related CMS examples in README ( #73247 )
...
## What?
Add missing related CMS examples and sort them.
## Why are
[cms-keystonejs-embedded](https://github.com/vercel/next.js/tree/canary/examples/cms-keystonejs-embedded )
and
[cms-strapi](https://github.com/vercel/next.js/tree/canary/examples/cms-strapi )
lacking?
Because these have only README.md file.
## How?
Update with the following text.
```md
- [AgilityCMS](/examples/cms-agilitycms)
- [Builder.io](/examples/cms-builder-io)
- [ButterCMS](/examples/cms-buttercms)
- [Contentful](/examples/cms-contentful)
- [Cosmic](/examples/cms-cosmic)
- [DatoCMS](/examples/cms-datocms)
- [DotCMS](/examples/cms-dotcms)
- [Drupal](/examples/cms-drupal)
- [Enterspeed](/examples/cms-enterspeed)
- [Ghost](/examples/cms-ghost)
- [GraphCMS](/examples/cms-graphcms)
- [Kontent.ai](/examples/cms-kontent-ai)
- [MakeSwift](/examples/cms-makeswift)
- [Payload](/examples/cms-payload)
- [Plasmic](/examples/cms-plasmic)
- [Prepr](/examples/cms-prepr)
- [Prismic](/examples/cms-prismic)
- [Sanity](/examples/cms-sanity)
- [Sitecore XM Cloud](/examples/cms-sitecore-xmcloud)
- [Sitefinity](/examples/cms-sitefinity)
- [Storyblok](/examples/cms-storyblok)
- [TakeShape](/examples/cms-takeshape)
- [Tina](/examples/cms-tina)
- [Umbraco](/examples/cms-umbraco)
- [Umbraco heartcore](/examples/cms-umbraco-heartcore)
- [Webiny](/examples/cms-webiny)
- [WordPress](/examples/cms-wordpress)
- [Blog Starter](/examples/blog-starter)
```
CC: @samcx
### 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: Sam Ko <sam@vercel.com >
2024-12-10 06:22:34 +00:00
e9c4a756a8
examples: remove next-env.d.ts files ( #73673 )
...
## Summary
Remove `next-env.d.ts` file from [the
examples](https://github.com/vercel/next.js/tree/canary/examples )
directory because gitignore template includes them.
## Description
At #41041 , removed `next-env.d.ts` files.
However, #47241 reintroduced them.
`create-next-app` makes `next-env.d.ts` file in the example directory if
it's typescript.
https://github.com/vercel/next.js/blob/c2078d0c05a03e9fde449a01ff2a10afbdad48bb/packages/create-next-app/create-app.ts#L202-L209
Therefore, `next-env.d.ts` file isn't necessary.
CC: @samcx
### 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 <jj@jjsweb.site >
2024-12-09 06:36: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 <1939140+ztanner@users.noreply.github.com >
2024-11-07 14:42:24 -08: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 <jj@jjsweb.site >
2024-10-29 19:44:50 +00:00
1948f5b4ba
fix(create-next-app): link to app dir docs in next-env.d.ts in app dir templates ( #68534 )
...
Fixes #68533
A link to docs in `next-dev.d.ts` linked to the pages router docs in app
router templates. This was confusing, because some sections on this page
only work with pages router. This PR fixes that
---------
Co-authored-by: Sam Ko <sam@vercel.com >
2024-08-09 22:21:28 +00:00
4466ba436b
chore(examples): use default prettier for examples/templates ( #60530 )
...
## Description
This PR ensures that the default prettier config is used for examples
and templates.
This config is compatible with `prettier@3` as well (upgrading prettier
is bigger change that can be a future PR).
## Changes
- Updated `.prettierrc.json` in root with `"trailingComma": "es5"` (will
be needed upgrading to prettier@3)
- Added `examples/.prettierrc.json` with default config (this will
change every example)
- Added `packages/create-next-app/templates/.prettierrc.json` with
default config (this will change every template)
## Related
- Fixes #54402
- Closes #54409
2024-01-11 16:01:44 -07:00
a3aa6590ff
chore(next/image)!: mark domains as deprecated in favor remotePatterns ( #57062 )
...
We already had `domains` as "not recommended" but this PR marks it as "deprecated" and prints a warning if its detected.
I also updated all examples to switch from `domains` to `remotePatterns`.
2023-10-19 20:24:48 +00:00
37b5cea794
chore: NextJS -> Next.js ( #55961 )
2023-09-25 14:53:11 +00:00
cca9dd1297
examples: Add new cms-payload example. ( #49616 )
...
This PR adds `cms-payload` to the examples folder. The demo provides a
NextJS frontend, built with Payload, which can be deployed together in a
single instance.
### Improving Documentation or adding/fixing 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: Lee Robinson <me@leerob.io >
Co-authored-by: JJ Kasper <jj@jjsweb.site >
2023-06-16 07:32:51 -07:00
Remco Haszing
