hanzoai/next.js
2
0
Fork 0
mirror of https://github.com/hanzoai/next.js.git synced 2026-09-24 17:00:51 +00:00
Code Issues Packages Projects Releases Wiki Activity
34,980 Commits 3 Branches 3,979 Tags
canary
Commit Graph
100 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Sam KoandGitHub 5c34f87bbe chore: update formatted duration string magnitude for millisconds <-> microseconds (#85136) 
## Why?

This PR refines the duration formatting logic in the build process:

1. Changed the millisecond threshold from 1ms to 2ms for better
readability
2. Fixed comparison operators from `>` to `>=` to ensure consistent
behavior at threshold boundaries
3. Updated documentation to reflect the new 2ms threshold

These changes ensure durations are displayed with appropriate units and
precision across all time ranges.
 2025-10-20 16:50:23 -07:00
Sam KoandGitHub 49ba0acc18 chore(examples): remove examples that can be v0'd (#77349) 
## Why?

Taking small steps towards reducing the large burden we are taking on with [examples](https://github.com/vercel/next.js/tree/canary/examples).
 2025-04-02 14:27:08 -07:00
Sam KoandGitHub cca78ec948 docs(scripts): missing 'soon' (#77137) 
## Why?

Follow up to https://github.com/vercel/next.js/pull/77136
 2025-03-14 13:18:57 -07:00
Sam KoandGitHub 83021c5a1d docs(scripts): update Script -> beforeInteractive docs (#77136) 
## Why?

The current documentation is misleading about how `beforeInteractive` does **not** block page hydration from occurring. Users should look to [this](https://github.com/vercel/next.js/pull/76916) for synchronously blocking scripts before hydration.
 2025-03-14 12:54:24 -07:00
Sam KoandGitHub 625f9b08b1 chore(github): add Not Found label (#77097) 
## Why?

Add the `Not Found` label for `not-found.tsx` file and `notFound()` function cases.
 2025-03-13 13:18:18 -07:00
Sam KoandGitHub 0aa0ef676d chore(github): remove /examples from contribution guidelines, remove examples issue template (#77050) 
## Why?

Start the prep-work for removing/moving [Next.js examples](https://github.com/vercel/next.js/tree/canary/examples).

Today, a lot of these examples already have their own dedicated location in their respective GitHub orgs.

These examples are also now present in other locations.

- https://github.com/nextjs
- https://v0.dev/chat/community
- https://vercel.com/templates/next.js
 2025-03-12 15:32:29 -07:00
Sam KoandGitHub eb53f79553 docs(use-cache): add invalidating section to use cache docs (#76958) 
## Why?

The cacheTag mention [here](https://nextjs.org/docs/app/api-reference/directives/use-cache#revalidating) makes it seem like cacheTag does the "revalidating," but actually this is still revalidateTag's job.

- Related: https://github.com/vercel/next.js/issues/76581
 2025-03-10 17:54:50 -07:00
Sam KoandGitHub dd4aca4bc3 chore(github): add moar labels (#76922) 
## Why?

We're missing some still!

- Add `After`, `Connection`, `Cookies`, `Headers`
- Remove `Package Managers`
 2025-03-07 20:34:37 -08:00
Sam KoandGitHub 0abd87717f docs(errors): remove confusing good-to-know since global-errors.tsx also show in dev as of 15.2 (#76825) 
## Why?

The "Good to know" has a typo, and it is probably better not mentioned. The https://nextjs.org/docs/app/building-your-application/routing/error-handling#handling-global-errors page does not mention (the fact that `global-errors.tsx` now show in `next dev`) it either.
 2025-03-05 04:52:45 -08:00
Sam KoGitHubLee Robinson
 		8c33e482de chore(cna): update tailwind styles to be closer to non-tw cna (#76647) 
## Why?

Updating Tailwind templates to closer match the non-Tailwind template.

(before, `localhost:3000` is current Tailwind template)


https://github.com/user-attachments/assets/b5bef4c7-0c22-43e2-87f1-2dbd4903ea0f

(after)


https://github.com/user-attachments/assets/5b1d087c-60e6-45fc-b749-f3894834e339

- Minor fix to `a.secondary` style's `min-width` to be the same width as
`a.primary`
-

---------

Co-authored-by: Lee Robinson <[email protected]>
 2025-03-04 09:34:33 -06:00
Sam KoandGitHub 0940320743 chore(github): move top prs and feature requests to different Slack channel (#76764) 
## Why?

Re-organizing some information across internal Slack channels.
 2025-03-03 11:35:56 -08:00
Sam KoandGitHub 7135484dac chore(cna): fix theme extend for tailwind v4 (#76583) 
## Why?

We are not extending the tailwind theme for `--color-background` and `--color-foreground`.

(Before)

https://github.com/user-attachments/assets/d336dab3-a00f-46cb-9587-055a6c5272fa

(After)


https://github.com/user-attachments/assets/123e829d-aa7e-4b57-aa21-261fc05350f8

Follow-up fix for https://github.com/vercel/next.js/pull/75407.
 2025-02-27 12:35:08 -08:00
Sam KoandGitHub 8dd0b56fb6 docs(errors): update suppressHydrationWarning section (#76521) 
## Why?

We should clarify that React will **not** attempt to patch mismatched text content when using `suppressHydrationWarning`.

- Related: https://github.com/reactjs/react.dev/pull/7651
- x-ref: https://github.com/vercel/next.js/discussions/75890
 2025-02-26 12:11:59 -08:00
Sam KoandGitHub 86ef885563 docs: adjust Caching data with an ORM or Database section (#76454) 
## Why?

Adjust first sentence of [Caching with an ORM or Database](https://nextjs.org/docs/app/building-your-application/data-fetching/fetching#caching-data-with-an-orm-or-database) section to clarify that you don't need `unstable_cache` to prerender a page.

- Fixes https://github.com/vercel/next.js/issues/73808
 2025-02-24 16:08:43 -08:00
Sam KoandGitHub a27d411037 docs(lazy-loading): add caveat to importing client components section (#76358) 
## Why?

Automatic code-splitting is currently not supported when a Server Component dynamically imports a Client Component.

- x-ref: https://github.com/vercel/next.js/issues/61066
- Fixes https://github.com/vercel/next.js/issues/60656
 2025-02-24 15:37:29 -08:00
Sam KoandGitHub 74c99d2b76 docs(cookies): update good-to-know for cookie.delete (#76303) 
## Why?

We should also clarify that the exact subdomain must be specified when using wildcard domains.

- Fixes https://github.com/vercel/next.js/issues/76275
 2025-02-20 15:35:35 -08:00
Sam KoandGitHub d55c00d842 docs(errors): minor update to failed-to-find-server-action error page (#76296) 
## Why?

Follow up to https://github.com/vercel/next.js/pull/75678#discussion_r1964355401.
 2025-02-20 13:57:36 -08:00
Sam KoandGitHub beb1f72e6d docs(errors): add failed-to-find-server-action error page (#75678) 
## Why?

We should also have an error page when somebody gets this error → https://github.com/vercel/next.js/blob/d70cac3eb4dee1d1361629d1b4c765365f184e26/packages/next/src/server/app-render/action-handler.ts#L1086.
 2025-02-20 12:31:59 -08:00
Sam KoandGitHub c939331bad chore(github): add Draft Mode area (#76249) 
## Why?

We don't cover Draft Mode issues with labels.
 2025-02-19 17:03:11 -08:00
Sam KoandGitHub c43d73dd24 chore(github): add Error Overlay area (#76167) 
## Why?

Adding an `Error Overlay` area (will add label as well) so we can start tracking issues with the new Error Overlay.
 2025-02-18 12:52:17 -08:00
Sam KoandGitHub 58e1adf4ca docs(css-in-js): update warning about using css-in-js with server components (#75931) 
## Why?

The warning suggests its not supported in Server Components, but since React 19 was released, there is better support! Need to just re-word the warning a bit.

- Fixes https://github.com/vercel/next.js/issues/75895

- https://nextjs.org/docs/app/building-your-application/styling/css-in-js
- https://react.dev/blog/2024/12/05/react-19#support-for-stylesheets
 2025-02-11 14:55:33 -08:00
Sam KoandGitHub a18f3ed514 chore(github): skip nissuer when Documentation issue template is used (#75802) 
## Why?

Issues with the `Documentation` **Type**, which is issues opened via the `Documentation` issue template, should not be prematurely closed with **Invalid Link** from [nissuer](https://github.com/balazsorban44/nissuer).
 2025-02-07 16:37:31 -08:00
Sam KoandGitHub ecc16d32c8 docs(route-segment-config): remove line in force-dynamic mentioning it's like getServerSideProps (#75773) 
## Why?

`force-dynamic` is not like `getServerSideProps` in Pages Router, so this bullet point needs to be removed.

- Fixes https://github.com/vercel/next.js/issues/75697
 2025-02-06 15:51:24 -08:00
Sam KoandGitHub a41d94a171 chore(github): add labels-to-add-when-unstale label -> not stale (#75721) 
## Why?

To track issues that are marked "not stale," we need to explicitly add a not stale label. https://github.com/actions/stale does not use this label by default.
 2025-02-06 12:26:34 -08:00
Sam KoandGitHub a9490686de chore(github): update stale bot (#75630) 
## Why?

A `days-before-issue-stale` period of two years has so far been successful. We can now move this to ~1.5 years (545 days).
 2025-02-03 17:51:40 -08:00
Sam KoandGitHub 2daa7e1fc8 chore(github): add conditional to triage workflow (#75524) 
## Why?

If an issue has the `stale` label, let's not run Nissuer.
 2025-02-03 15:04:22 -08:00
Sam KoandGitHub 9fc4d39aba chore(github): add more areas (#75456) 
## Why?

Not sure how I forgot `Route Handlers`.
 2025-01-29 15:39:47 -08:00
Sam KoandGitHub 51f9e2b263 chore(github): update github labels (#75452) 
## Why?

Rename `Output (export/standalone)` to `Output`. This keeps it separate from labels such as `Image (next/image)` (`export/standalone` is not an import).
 2025-01-29 15:00:48 -08:00
Sam KoandGitHub c97dff9ba1 chore(github): update more labels (#75444) 
## Why?

To better organize and triage issues.

## How?

- Remove `Link (next/link)`, update `Navigation` to `Linking and
Navigating`
- Add `Redirects`
 2025-01-29 11:53:32 -08:00
Sam KoandGitHub 3162fcda47 chore(github): update more labels (#75409) 
## Why?

Adding more labels so we can better triage and categorize issues.
 2025-01-28 13:19:56 -08:00
Sam KoandGitHub 90164a1001 chore(github): update more labels (#75382) 
## Why?

Updating more of our labels to better place issues into concrete areas.
 2025-01-27 18:20:33 -08:00
Sam KoandGitHub 1d5b8ae612 chore(github): add CSS area/label (#75201) 
## Why?

We should just use `CSS` instead of mixing `Webpack` and `Turbopack` issues together with "CSS" issues.
 2025-01-22 14:27:05 -05:00
Sam KoandGitHub 7ea552de52 chore(github): remove Developer Experience area (#75198) 
## Why?

The label is too broad and provides little help in filtering issues properly.
 2025-01-22 13:51:57 -05:00
Sam KoandGitHub d5500d7c8d chore(github): remove documentation label from area dropdown (#75008) 
## Why?

Follow-up on https://github.com/vercel/next.js/pull/75006. We want to instead use the `Documentation` **Type**.
 2025-01-16 14:29:38 -08:00
Sam KoandGitHub 3f7ac9c01a chore(github): use Issue Types (#75006) 
## Why?

Start using [**Issue Types**](https://github.com/orgs/community/discussions/139933) over **labels** for "labeling" which issue template was used.
 2025-01-16 14:10:01 -08:00
Sam KoandGitHub 885e70eb1a chore(github): fix days-before-issue-close/stale (#74838) 
## Why?

We mixed up `days-before-issue-close` and `days-before-issue-stale`.
 2025-01-13 17:35:55 -08:00
Sam KoandGitHub d737cefcc4 chore(github): ignore PRs in for stale issue bot (#74767) 
## Why?

We have to explicitly give a `-1` for `days-before-pr-close` and `days-before-pr-stale` in order to ignore sifting through PRs.

- https://github.com/vercel/next.js/actions/runs/12716117689/job/35449724177#step:2:376
 2025-01-10 12:57:37 -08:00
Sam KoandGitHub 36a138a421 chore(github): update how we handle stale issues (#73488) 
## Why?

We currently have no automated process for handling stale issues. This PR adds an automated process for this.
 2025-01-10 11:34:09 -08:00
Sam KoandGitHub 07e636f952 chore(github): switch back to STALE_TOKEN (#74723) 
## Why?

We have regenerated the token with necessary permission as `STALE_TOKEN`.
 2025-01-09 18:28:52 -08:00
Sam KoandGitHub 66059a4a14 docs(images): update distinction between priority and fetchPriority (#74650) 
## Why?

This [PR](https://github.com/vercel/next.js/pull/67351) de-coupled functionality between the Next.js-provided `priority` property and the native `<img>`-provided `fetchPriority` property.

We need to update the documentation to reflect this.
 2025-01-08 10:09:57 -08:00
Sam KoandGitHub 9b79c118e3 ci(eslint): remove unecessary react/self-closing-comp (#74120) 
## Why?

It turns out the `react/self-closing-comp` rule is not necessary to cover for JSX tags that are not properly closed.
 2025-01-07 11:24:39 -08:00
Sam KoandGitHub 0e6185e1b5 chore(github): update issue_stale token to release bot token (#74575) 
## Why?

Updating from `STALE_TOKEN` to `RELEASE_BOT_TOKEN` because `STALE_TOKEN` has expired.
 2025-01-06 19:52:49 -08:00
Sam KoandGitHub ca9af5bcad chore(examples): update React to stable 19 (#74499) 
## Why?

- Update React in reproduction example templates to stable v19
- Switch `.ts` for `next.config`
- Fixes https://github.com/vercel/next.js/issues/74422
 2025-01-06 17:32:37 -08:00
Sam KoandGitHub 41378d01e2 chore(github): update comments stale period (#74291) 
## Why?

Since we updated the stale waiting period in https://github.com/vercel/next.js/pull/73709, we need to update these comments as well.
 2024-12-26 15:07:58 -08:00
Sam KoandGitHub 61bfaa507c chore: add eslint check for mdx (#74009) 
## Why?

MDX changes are not getting properly linted, causing upstream issues.

When trying to push this incorrect change:

```
<Image
  alt="Route segments for dynamic MDX components"
  srcLight="/docs/light/mdx-files.png"
  srcDark="/docs/dark/mdx-files.png"
  width="1600"
  height="849"
>
```

![CleanShot 2024-12-16 at 16 14 00@2x](https://github.com/user-attachments/assets/bac31213-3996-4d56-ba35-be895c401671)
 2024-12-16 17:02:43 -08:00
Sam KoandGitHub 5b28aaa396 chore(github): fix wrong-issue-template body (#74003) 
## Why?

The automated comment should be a paragraph, not a single line code-snippet.
 2024-12-16 14:20:07 -08:00
Sam KoGitHubLee Robinson
 		21fa7730cf docs(mdx): add a dynamic imports section for App Router (#73466) 
## Why?

Adding a section dedicated to dynamically importing MDX files inside
pages for App Router.

- x-ref: https://github.com/vercel/next.js/discussions/70417

---------

Co-authored-by: Lee Robinson <[email protected]>
 2024-12-13 18:30:00 -06:00
Sam KoandGitHub 8e64b2cfe2 chore(github): add issue_wrong_template workflow (#73882) 
## Why?

Mini-automation to automatically close issues when using the `please use the correct issue template` label.
 2024-12-13 15:25:49 -08:00
Sam KoandGitHub c92e845296 chore(github): fix typo in close-issue-message (#73878) 
## Why?

Fix typo.
 2024-12-12 22:28:23 -08:00
Sam KoandGitHub 0c78009841 chore(github): update stale issue periods (#73709) 
## Why?

We should be more aggressive with how we close issues.

- Update the stale waiting period for `please add a complete reproduction` to 2 days
- Update the stale waiting period for `please simplify reproduction` to 14 days
- Update the stale waiting period for `please verify canary` to 14 days
 2024-12-09 20:51:58 -08:00
Sam KoandGitHub b7c271d708 test: fix next-sass test (#73633) 
## Why?

This [PR](https://github.com/vercel/next.js/pull/73548) updated the directory of an example (it's now `examples/with-sass`), and it broke a test.
 2024-12-06 16:41:37 -08:00
Sam KoandGitHub f24c4f5ff2 chore(examples): update api-routes-cors (#73408) 
## Why?

`package.json` and `tsconfig.json` are dated.

- x-ref: https://github.com/vercel/next.js/pull/73338
 2024-12-02 17:06:32 -08:00
Sam KoandGitHub 18e8bfbbdb chore(cna): add .pnpm-debug.log* to all cna gitignore (#73446) 
## Why?

We may as well include a `.pnpm-debug.log` since it's possible to create Create Next App with [pnpm](https://pnpm.io/).
 2024-12-02 15:29:29 -08:00
Sam KoandGitHub 48e7ff59da docs: clarify Switching to Dynamic Rendering section (#73113) 
## Why?

The default config of fetch, which is `auto no cache`, is slightly different from the fetch option `{ cache: 'no-store' }` (this opts the whole route out of statically prerendering), so we need to clarify that further.

- https://nextjs.org/docs/canary/app/api-reference/functions/fetch#optionscache
- x-ref: https://github.com/vercel/next.js/pull/72982
- Fixes https://github.com/vercel/next.js/issues/73109
 2024-11-22 16:02:16 -08:00
Sam KoandGitHub 915efdd764 docs(routing): update params type to be async (v15) (#73111) 
## Why?

Update params type to be async (v15).

- x-ref: https://github.com/vercel/next.js/pull/72070
 2024-11-22 15:22:03 -08:00
Sam KoandGitHub 3ba49c7514 docs: update tags when upgrading from 13 to 14 (#73071) 
## Why?

The `latest` tag currently points to v15, so we need to update the tag to `next-14`.
 2024-11-21 15:55:20 -08:00
Sam KoandGitHub a40dd63cf4 docs(next-config): add experimental inline css docs (#73070) 
## Why?

Add documentation for experimental `inlineCss`.

```
import type { NextConfig } from 'next'

const nextConfig: NextConfig = {
  experimental: {
    inlineCss: true,
  },
}
```

- x-ref: https://github.com/vercel/next.js/pull/72195
 2024-11-21 15:34:46 -08:00
Sam KoandGitHub 2fcb741d7f docs(fetch): clarify default fetch behavior (#72982) 
## Why?

The default fetch behavior, which is shown as `auto no cache` when you
set the config
[logging](https://nextjs.org/docs/app/api-reference/next-config-js/logging)
to `true`, essentially means fetch once on `next build` to prerender the
page. But, when a [Dynamic
API](https://nextjs.org/docs/app/building-your-application/rendering/server-components#dynamic-rendering)
is used, it will fetch from the resource on every request.

This is different from `{ cache: 'no-store' }`, which regardless of
whether Dynamic APIs are used, will de-op the page from prerendering.
 2024-11-21 15:50:39 +00:00
Sam KoandGitHub a3960c2188 docs(sitemap): remove extra 's' (#73023) 
## Why?

There's a typo in the note—Route Handler should be singular.
 2024-11-20 14:32:04 -08:00
Sam KoGitHubJJ Kasper
 		9a591a0112 chore(build): remove injecting fast refresh to custom loader logs (#72870) 
## Why?

Removing a log that holds very little meaning these days.


![cleanshot_2024-11-03_at_09.13.12_2x.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/FEMDaE9e61ZMCiJM0S0I/ef9c17a7-4fd1-4c70-94c3-c2b31f10c357.png)

Co-authored-by: JJ Kasper <[email protected]>
 2024-11-18 15:45:33 +00:00
Sam KoandGitHub 90cd4e0635 examples(with-supabase): fix action type error (#72783) 
## Why?

There is a type issue with one of the form actions.

```
app/(auth-pages)/sign-up/page.tsx:42:25 - error TS2322: Type '(formData: FormData) => Promise<{ error: string; }>' is not assignable to type 'string | ((formData: FormData) => void | Promise<void>) | undefined'.
  Type '(formData: FormData) => Promise<{ error: string; }>' is not assignable to type '(formData: FormData) => void | Promise<void>'.
    Type 'Promise<{ error: string; }>' is not assignable to type 'void | Promise<void>'.
      Type 'Promise<{ error: string; }>' is not assignable to type 'Promise<void>'.
        Type '{ error: string; }' is not assignable to type 'void'.

42           <SubmitButton formAction={signUpAction} pendingText="Signing up...">
```

- x-ref: https://github.com/vercel/next.js/discussions/72778
 2024-11-13 14:19:19 -08:00
Sam KoandGitHub 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
Sam KoandGitHub a42205401e fix(next/font): update axes error logic (#72442) 
## Why?

The current error message when you have have a set `weight: ['400', '700']` and set `axes: ['wdth']` for a variable font is confusing—it should mention to correct your weight property (e.g., `weight: 'variable'` or nothing at all for `weight`).

- Fixes https://github.com/vercel/next.js/issues/72413
 2024-11-07 15:35:29 -08:00
Sam KoandGitHub 3b5b5a25a9 docs(output): update standalone docs with cp and start commands (#72432) 
## Why?

We're not documenting a way to manually move files to `.next/standalone` for `output: 'standalone'`.
 2024-11-06 14:50:14 -08:00
Sam KoandGitHub ea211a8788 docs(testing): update cypress note (v14 now supported) (#72366) 
## Why?

Cypress has supported v14 for a while.

- Fixes https://github.com/vercel/next.js/issues/72325
 2024-11-05 15:40:13 -08:00
Sam KoandGitHub daba014016 fix(webpack): update cssnano-preset-default to v7 (#68748) 
## Why?

Our default CSS minifier had a bug → https://github.com/cssnano/cssnano/issues/1655, which was also reported (below).

Since it is now fixed upstream, we need to update our cssnano in Next.js.

- Fixes https://github.com/vercel/next.js/issues/68476

## How?

- Update `cssnano-preset-default` to v6
- Add unit test to cover the case for being able to declare layer names

(the added unit test errors in an way that's unreadable on canary)
![CleanShot 2024-11-04 at 22 32 32@2x](https://github.com/user-attachments/assets/ef3a302a-2aec-4b63-9db2-40869daaf5ad)
 2024-11-04 22:36:39 -08:00
Sam KoandGitHub 8a0a3652d0 docs(fetch): update fetch example to v15 (#72295) 
## Why?

The default cache config for fetch is `{ cache: 'no-store' }` with v15.

- Fixes https://github.com/vercel/next.js/issues/72213
 2024-11-04 15:49:54 -08:00
Sam KoandGitHub 6cf63ff830 docs(use-cache): fix typo and link (#72292) 
## Why?

We have a typo and incorrect link.

- Fixes https://github.com/vercel/next.js/issues/72266
 2024-11-04 22:12:12 +00:00
Sam KoandGitHub 8b881a5465 chore(github): add dynamicIO label to issue template (#72154) 
## Why?

Add `dynamicIO` label to our issue template so we can start categorizing
those issues.
 2024-10-31 19:40:56 +00:00
Sam KoandGitHub 35a3eca34e fix: uri encode dynamic routes in dev (#71588) 
## Why?

In `next dev`, `404` errors are returned for dynamic routes that contain
characters that should be URI encoded in the path. The `404`s are not
present in `next build`.

## How?

We're failing to decode the
[`resolvedUrlPathname`](https://github.com/vercel/next.js/blob/ffec1d3a458056a4531e6b35518fca28bf9c3943/packages/next/src/server/base-server.ts#L2897)
in `next dev`, resulting in a `404`. So we add the same decoding logic
in development.

- Fixes https://github.com/vercel/next.js/issues/63002
 2024-10-29 14:51:45 -07:00
Sam KoandGitHub e54338a40d docs(turbo): add experimental icon to turbo config section (#71761) 
## Why?

The `turbo` config is still experimental in v15.

- Fixes https://github.com/vercel/next.js/issues/71750
- Related PR: https://github.com/vercel/next.js/pull/71755
 2024-10-23 15:56:05 -07:00
Sam KoandGitHub b3d7335d0a docs(ppr): update note about ppr (#71697) 
## Why?

Let's clarify this is only available in canary. We need to remove it
from the stable docs later.
 2024-10-23 11:50:53 -07:00
Sam KoandGitHub c1cfee3e1d docs(next-config): remove mention of appIsrStatus is on canary (#71695) 
## Why?


[`appIsrStatus`](https://nextjs.org/docs/canary/app/api-reference/next-config-js/devIndicators#appisrstatus-static-indicator)
is stable now, so this note is no longer necessary.
 2024-10-23 05:40:20 +00:00
Sam KoandGitHub 8520404cf6 docs(ppr): remove v14 mention for ppr (#71498) 
## Why?

For PPR (experimental), user's should just opt to use v15 canary if they
want to try out PPR. Removing the v14 mention reduces this confusion.

- x-ref:
https://vercel.slack.com/archives/C05KYT5S9FF/p1729264052080029?thread_ts=1729263181.989139&cid=C05KYT5S9FF
 2024-10-21 20:36:59 +00:00
Sam KoandGitHub bf3755dbd7 docs(route-groups): add an example about opting loading skeletons to a specific route (#71328) 
## Why?

Add an additional example that highlights using Route Groups to opt a
loading skeleton to a specific route.

- Fixes: https://github.com/vercel/next.js/issues/71321
 2024-10-18 12:57:32 -07:00
Sam KoandGitHub 0901b79be0 chore(github): update schema from url → html_url (#71429) 
## Why?

Currently, `url` would just use the GitHub API url (JSON response of
issue), not the issue's html url, which is the correct html link to the
issue. We want the html link instead.
 2024-10-17 09:20:45 -07:00
Sam KoGitHubZack Tanner
 		bed511c774 docs(link): add mention about how App Router prefetches on hover (#70679) 
## Why?

There is no mention of how App Router uses hover for prefetching
(`null`, and `true`). There is only a mention of hover for the `false`
state.

---------

Co-authored-by: Zack Tanner <[email protected]>
 2024-10-01 22:07:29 +00:00
Sam KoGitHubWill Binns-Smith
 		c38bcb7170 docs(cli): add mention of default port with experimental-https (#70497) 
## Why?

There is no mention of what the default port is when you `next dev
--experimental-https`.

x-ref: https://x.com/rauchg/status/1839092783392632867

---------

Co-authored-by: Will Binns-Smith <[email protected]>
 2024-09-25 21:34:39 -07:00
Sam KoGitHubZack TannerJJ Kasper
 		a189a4d9e4 chore(sass): add docs for implementation property in sassOptions and update sassOption types (#70428) 
## Why?

We currently don't document the `implementation` property for
`sassOptions`. Since this is one our maintained properties, we should
also update the types for `sassOptions`.

- Fixes https://github.com/vercel/next.js/issues/70020

---------

Co-authored-by: Zack Tanner <[email protected]>
Co-authored-by: JJ Kasper <[email protected]>
 2024-09-25 17:51:23 -07:00
Sam KoandGitHub 75c46b5d37 refactor(github): popular-prs workflow (#70414) 
## Why?

- Refactor popular-prs workflow to `.ts`
- Bump packages
 2024-09-24 21:26:44 +00:00
Sam KoGitHubJJ Kasper
 		ac9a51465b chore: throw error when trying to use next.config.mts/.cjs/.cts (not supported yet) (#70376) 
## Why?

We should update our documentation and also throw an error if somebody
tries to use the `.mts` ( ES Module TypeScript) extension with
`next.config`. We currently don't support this extension.

- Fixes: https://github.com/vercel/next.js/issues/70201

---------

Co-authored-by: JJ Kasper <[email protected]>
 2024-09-24 18:58:11 +00:00
Sam KoGitHubZack Tanner
 		908b419af9 docs(parallel): clarify why separate slots cannot be static and dynamic at the same route segment level (#70386) 
## Why?

Currently, we do not explain why you cannot have a separate static and
dynamic slot at the same route segment level.

- Fixes https://github.com/vercel/next.js/issues/70366

---------

Co-authored-by: Zack Tanner <[email protected]>
 2024-09-24 10:25:25 -07:00
Sam KoGitHubJJ Kasper
 		c4ccacee89 docs(ppr): Add note about canary for PPR (#70053) 
## Why?

Experimental PPR does not work for Next.js v14. Technically, you can try
using v14 canary, but at that point, you should just be using v15 canary
because both requires React v19.

- Fixes https://github.com/vercel/next.js/issues/69791

---------

Co-authored-by: JJ Kasper <[email protected]>
 2024-09-13 21:00:13 +00:00
Sam KoGitHubJJ Kasper
 		b57e814701 docs(route-handlers): add note about caching with other support HTTP methods in Route Handlers (#70049) 
## Why?

We currently do not clarify that other supported HTTP Methods (all other
besides `GET`) in Route Handlers are not cached. This remains true even
if they are placed alongside a `GET` that is cached.

---------

Co-authored-by: JJ Kasper <[email protected]>
 2024-09-12 15:20:30 -07:00
Sam KoGitHubTim Neutkens
 		dab529ea6b chore(github): be more explicit about having to check canary (#69934) 
## Why?

Issues are still getting created where folks are not testing on the
latest canary. We'll add more explicit language to emphasize the need to
test on canary as well.

---------

Co-authored-by: Tim Neutkens <[email protected]>
 2024-09-12 12:58:15 -07:00
Sam KoandGitHub 8f90c352d2 chore(github): reduce per_page to 25 for issues-by-version (#69974) 
## Why?

We're running into the GitHub rate limit when querying for 50
`per_page`, so reducing to 25.

Also adding logic throw a `info(...)` message when no issues by <xyz>
version are found.
 2024-09-11 20:49:12 +00:00
Sam KoandGitHub f760882f06 chore(github): update channel for popular-issues (#69941) 
## Why?

Updating the channel for popular issues. The updated channel will serve
the action's purpose better than its current channel.
 2024-09-10 23:24:56 +00:00
Sam KoandGitHub 23c4cf0c2f docs(revalidate): add not about revalidate in Development (#69898) 
## Why?

There is no mention that Pages are rendered on demand in Development,
regardless if you use this route segment config.

```
export const revalidate = 10
```
 2024-09-10 03:41:56 -07:00
Sam KoandGitHub f9148a2a0d docs(link): additional updates with regards to scrolling behavior in App Router (#69896) 
## Why?

Adding onto this → https://github.com/vercel/next.js/pull/69894.

A feel more additions to clarify the scroll behavior in App Router.

## How?

- Remove instances of previous, incorrect way of describing the default
scroll behavior
- Remove **Disabling Scroll Restoration** section
- Refactor **Disable scrolling to the top of the page** section
 2024-09-09 16:49:35 -07:00
Sam KoandGitHub 2b9f1bcb61 chore(cna): re-add /public (#69887) 
## Why?

To prevent confusion about the `/public`, re-adding to Create Next App. 

x-ref: https://x.com/YTCodeAntonio/status/1832856105447473351
 2024-09-09 22:48:46 +00:00
Sam KoandGitHub 644b6c6176 docs(link): update scroll docs (#69894) 
## Why?

The current docs on scrolling behavior when using `<Link>` are
misleading and incorrect. This edit correctly documents the expected
scrolling behavior (in both `true` or `false` cases).

- https://nextjs.org/docs/app/api-reference/components/link#scroll
 2024-09-09 13:36:58 -07:00
Sam KoandGitHub 3bb7415f38 chore(github): add issues_version.yml workflow (#69810) 
## Why?

A manual workflow that will query issues by version string (e.g.,
`14.2.8`), then output the relevant issues to Slack.

x-ref: https://vercel.slack.com/archives/C04LGE5SYEB/p1725659202909009
 2024-09-06 19:18:24 -07:00
Sam KoandGitHub 1b89d7dcee refactor(github): refactor triage-issues-with-ai to generateObject (#69696) 
## Why

It turns out we should have been using `generateObject()` instead all
along for this use case.

![CleanShot 2024-09-04 at 14 18
31@2x](https://github.com/user-attachments/assets/033d51f3-12a1-47af-8967-67e365ba2ead)
 2024-09-04 21:59:19 +00:00
Sam KoandGitHub 12cbab273c docs(usePathname): add note about using usePathname with rewrites (#69686) 
## Why?

A `useState` + `useState` need to be used with `usePathname` when the
route is rewritten to. Adding this as a note to our documentation.

- x-ref:
https://github.com/vercel/next.js/pull/69631#pullrequestreview-2278118356
 2024-09-04 17:08:17 +00:00
Sam KoandGitHub b70d3572bf chore(metadata): add clarifying comment (#69549) 
## Why?

Adding a clarification comment in case somebody finds this the
[warning](https://github.com/vercel/next.js/blob/397a3eb475c75a38ab6178e269e0bbb3d1dd84f7/packages/next/src/lib/metadata/resolvers/resolve-opengraph.ts#L137)
in their Vercel Deployment, and goes back to the code to see why they're
seeing it.
 2024-09-03 17:55:34 +00:00
Sam KoandGitHub d3f5532065 fix: styledComponents schema (#69230) 
## Why?

Both the `topLevelImportPaths` and `meaninglessFilenames` should not
need a minimal of 1 item in their arrays.

- Fixes https://github.com/vercel/next.js/issues/68573
 2024-09-02 08:27:55 +00:00
Sam KoandGitHub e71b7b5acd chore(github): fix tool call (#69470) 
## Why?

Because there was no `execute` properly in the Tool Call, the Tool Call
was not immediately executed. Hence, the AI was ending with "_will_
report to Slack."

## How?

Re-add the execute property.
 2024-08-29 16:18:27 -07:00
Sam KoandGitHub 26a8824515 chore(github): update deprecated property in triage issues with ai (#69323) 
## Why?

It's possible that the `maxAutomaticToolTrips` line is affecting
`generateText()` from having a `results.roundtrips.length > 1` (how to
identify when a Tool Call is made), which is how the Slack message gets
sent.

- `maxAutomaticToolTrips` → `maxToolRoundtrips`
-
https://github.com/vercel/next.js/actions/runs/10525787598/job/29271187944
 2024-08-26 13:04:29 -07:00
Sam KoGitHubDelba de Oliveira
 		bf2de9362c docs: add useLightningcss config (#69161) 
## Why?

We don't have any documentation about the experimental `next.config.ts`
config `useLightningcss`.

- Fixes: https://github.com/vercel/next.js/issues/69030

Co-authored-by: Delba de Oliveira <[email protected]>
 2024-08-23 14:09:28 +01:00
Sam KoandGitHub e1b889fd9f chore(github): update reactionSchema (#69203) 
## Why?

The GitHub documentation schema for issues → opened is incorrect for
`reactions`. Not entirely sure if this will fix the errored action
(error is truncated?), but this was the only issue I found.

-
https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=opened#issues
-
https://github.com/vercel/next.js/actions/runs/10510363688/job/29118781461
 2024-08-22 15:08:41 -07:00