- 18 3月, 2021 8 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tobias Koppers 提交于
as vercel doesn't allow env vars starting with _
-
由 Tobias Koppers 提交于
-
由 Tobias Koppers 提交于
-
由 Tobias Koppers 提交于
This allows to use `__NEXT_WEBPACK_LOGGING` to enable verbose webpack logging output to investigate into performance and cache problems. `__NEXT_WEBPACK_LOGGING=1` enables some basic logging `__NEXT_WEBPACK_LOGGING=infrastructure` enables only infrastructure logging `__NEXT_WEBPACK_LOGGING=profile-client` enables deep profile output of the client build `__NEXT_WEBPACK_LOGGING=profile-server` same for the server `__NEXT_WEBPACK_LOGGING=profile-client,infrastructure` combines multiple things
-
由 Lee Robinson 提交于
And an improved design
😄 https://roadmap-redis.vercel.app/ -
由 Josh Flayhart 提交于
It's currently misleading and I chose to freeze to a particular version since pointing to canary every time is likely to break (as is happening prior to this PR). The link will now go to: https://github.com/vercel/next.js/blob/v10.0.8/packages/next/next-server/server/config-shared.ts#L33
-
由 Mokshit Jain 提交于
I have added a new section to the `with-redux-toolkit` example on setting up Typescript with Redux Toolkit and React-Redux. It links the redux toolkit documentation and Next.js documentation on adding Typescript to a Next.js project.
-
- 17 3月, 2021 8 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tobias Koppers 提交于
update webpack, fix runtime location, fix undeclared variable, omit env vars from cache version (#23113) * this will fix problems with serverless target which doesn't use a runtime chunk * It also omit env vars from contributing to cache version as webpack will handle that now * It moves the webpack-runtime chunk from ./chunks back to ./
-
由 JJ Kasper 提交于
-
由 Shu Ding 提交于
This PR upgrades `jest-worker` and `jest-cli` to the latest pre-release version, also removed `jest-circus` which is included in Jest by default. `jest-worker@next` includes a fix for memory leak that we need (https://github.com/facebook/jest/pull/11187). Fixes #22925. This will also improve the OOM issue for `next dev` #15855.
-
由 Mokshit Jain 提交于
I have simplified the `with-redux-toolkit` example and changed the directory structure to "feature folders". I have removed the `notes` page and API route as it wasn't directly related to the redux toolkit. This example is also identical to the official [cra redux template](https://github.com/reduxjs/cra-template-redux). All the dependencies have also been updated.
-
由 Lee Robinson 提交于
Supersedes https://github.com/vercel/next.js/pull/23115 for more clarity and a better recommendation.
-
由 Shane Rogers 提交于
I similarly [couldn't find this info](https://github.com/vercel/next.js/issues/19711#issuecomment-750414110) in the docs about configuring the image path when using an app `basePath`, so thought I'd add it.
-
由 Abdullah Mzaien 提交于
- `scroll` - Optional boolean, controls scrolling to the top of the page after navigation. Defaults to `true` and - `scroll`: Scroll to the top of the page after a navigation. Defaults to `true` as options for router.push
-
- 16 3月, 2021 10 次提交
-
-
由 René Keller 提交于
Fixes "Type 'string' is not assignable to type 'number'." TS warning
-
由 JJ Kasper 提交于
-
由 Shu Ding 提交于
Reverts vercel/next.js#23082
-
由 JJ Kasper 提交于
-
由 Shu Ding 提交于
Reverts vercel/next.js#20428 temporarily to move this feature into the next canary release.
-
由 Kyle Boss 提交于
# Route Announcements ## Summary This PR improves the accessibility of NextJS's client-side navigation by announcing route changes to screen readers. ## Context When a user who is sighted clicks on a link, they can see the content change. It's an affirmation that what the user intended to do by clicking a link actually worked! Users navigating the page via a screen-reader will not get this feedback on NextJS sites (This is an issue on many SPA-like architectures). https://user-images.githubusercontent.com/4213649/103017382-63b02b00-44f8-11eb-9940-fb530d2d3018.mov ## Solution Whenever there is a route change, the new `<RouteAnnouncer />` will look for a name to give the new page and then announce it! The name is found by first looking for an `h1`, falling back to `document.title`, and lastly to `pathname`. `<RouteAnnouncer />` is a visually hidden component placed within the `<AppContainer />`. ## Demo https://user-images.githubusercontent.com/4213649/103017401-6ad73900-44f8-11eb-8050-b3e9a7e0c3f2.mov ## Inspiration First and foremost, this PR was inspired by @marcysutton's studies and writing, [What we learned from user testing of accessible client-side routing techniques with Fable Tech Labs ](https://www.gatsbyjs.com/blog/2019-07-11-user-testing-accessible-client-routing/) as well as @madalynrose's [Accessible Routing](https://github.com/gatsbyjs/gatsby/pull/19290) PR for Gatsby. There were also learnings gleaned from the conversations within #7681. ### Related Issues & PRs - Resolves #7681 - Relates to #19963
-
由 JJ Kasper 提交于
-
由 Lee Robinson 提交于
-
由 Lee Robinson 提交于
Also put current maintainers at the top of the list.
-
- 15 3月, 2021 1 次提交
-
-
由 Alex Safian 提交于
The `path` variable must be an array of objects which has a `params` key. This code will prevent reader confusion.
-
- 14 3月, 2021 1 次提交
-
-
由 JJ Kasper 提交于
This fixes index data route loading for i18n with `trailingSlash: true` enabled and also fixes prerendering `asPath` values not containing a trailingSlash when enabled. Fixes: https://github.com/vercel/next.js/issues/17813 Fixes: https://github.com/vercel/next.js/issues/22747
-
- 13 3月, 2021 1 次提交
-
-
由 Karthikeyan Ranasthala 提交于
This is an example on how to use styled-jsx with content security policy.
-
- 12 3月, 2021 7 次提交
-
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This makes sure we don't trigger the export step if we aren't exporting any static pages during a build. This also adds an invariant to ensure we don't attempt creating a progress with 0 items. Fixes: https://github.com/vercel/next.js/issues/22994
-
由 Kenneth Lum 提交于
changing `props: posts` to `props: { posts }`
-
由 Kenneth Lum 提交于
When there is data already, the props is props: { data } Would be better if the `props: { }` part is `props: { data }`
-
由 JJ Kasper 提交于
This adds a note to the environment variables documentation to mention how the env files can be loaded using the `@next/env` package as this has been brought up a few times. x-ref: https://github.com/vercel/next.js/issues/22936#issuecomment-796665303 x-ref: https://github.com/vercel/next.js/issues/17903
-
由 JJ Kasper 提交于
-
由 Dale Bustad 提交于
These messages aren't necessary in the normal course of using Next.js. Hiding behind a flag to reduce the noise.
-
- 11 3月, 2021 4 次提交
-
-
由 Nabil Boussouf 提交于
Set tailwindcss as a development dependency https://tailwindcss.com/docs/guides/nextjs#install-tailwind-via-npm
-
由 JJ Kasper 提交于
-
由 Dale Bustad 提交于
A number of changes here. I recommend viewing the diff with the <a href="?w=1">whitespace flag enabled</a>. - OpenTelemetry is replaced with a custom and lightweight tracing solution. - Three trace targets are currently supported: console, Zipkin, and NextJS. - Tracing is now governed by environment variables rather than `--require instrument.js`. + `TRACE_TARGET`: one of `CONSOLE`, `ZIPKIN`, or `TELEMETRY`; defaults to `TELEMETRY` if unset or invalid. + `TRACE_ID`: an 8-byte hex-encoded value used as the Zipkin trace ID; if not provided, this value will be randomly generated and passed down to subprocesses. Other sundry: - I'm missing something, probably a setup step, with the Zipkin target. Traces are captured successfully, but you have to manually enter the Trace ID in order to view the trace - it doesn't show up in queries. - I'm generally unhappy with [this commit](https://github.com/vercel/next.js/pull/22713/commits/235cedcb3ead76b630b4c8aa695f904489da2831). It is... untidy to provide a telemetry object via `setGlobal`, but I don't have a ready alternative. Is `distDir` strictly required when creating a new Telemetry object? I didn't dig too deep here. As noted, there are a lot of changes, so it'd be great if a reviewer could: - [ ] pull down the branch and try to break it - [ ] check the Zipkin traces and identify possible regressions in the functionality Closes #22570 Fixes #22574
-
由 Lee Robinson 提交于
-