- 05 10月, 2020 7 次提交
-
-
由 JJ Kasper 提交于
Follow-up to https://github.com/vercel/next.js/pull/17538 per https://github.com/vercel/next.js/pull/17538#discussion_r499647323 this updates the check to use the existing `hasNextSupport` export instead of checking the environment variable directly
-
由 James George 提交于
Added a test case to make sure that creating a new project within the current directory works as expected.
-
由 JJ Kasper 提交于
Follow-up to https://github.com/vercel/next.js/pull/17533 this makes sure the file used to signal release stats should be skipped for a non-release merge is created in a location that is accessible by the stats action and also updates the release action info detection for the new workflow
-
由 JJ Kasper 提交于
This makes sure to normalize the params for optional catch-all routes on Vercel since for `fallback: true` pages the `[[...paramName]]` value will be provided for the undefined/root param which needs to be normalized. Tests have been added in https://github.com/vercel/vercel/pull/5247 and were manually tested with the changes in this PR with https://github.com/ijjk/next-update-loader Fixes: https://github.com/vercel/next.js/issues/17220 x-ref: https://github.com/vercel/vercel/pull/5247
-
由 JJ Kasper 提交于
This adds a warning when `next export` and custom routes are defined outside of a platform that supports them since they won't be applied anymore.
-
由 Rafael Zerbini 提交于
Fixes #16431 * Added `.babelrc` with `next/babel` to remove the need of the React import on the `with-storybook` example.
-
由 JJ Kasper 提交于
Noticed this method was left-over from previous query handling logic in `api-utils` while working on https://github.com/vercel/next.js/pull/17370 so this removes the extra code which should be safe since `api-utils` is an internal file that shouldn't be relied on externally.
-
- 03 10月, 2020 3 次提交
-
-
由 Joris W 提交于
The page describing exportPathMap goes straight into an example without explaining what the config is for.
-
由 JJ Kasper 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Riccardo Di Maio 提交于
-
- 02 10月, 2020 4 次提交
-
-
由 Yann Pringault 提交于
-
由 JJ Kasper 提交于
This adds a note about public files and pages taking higher priority over rewrites causing them to not be able to be rewritten unless the files are renamed first since this has been asked a few times. x-ref: https://github.com/vercel/next.js/discussions/17513 x-ref: https://github.com/vercel/next.js/discussions/9081#discussioncomment-22077 x-ref: https://github.com/vercel/next.js/discussions/9081#discussioncomment-21995
-
由 Dylan Jhaveri 提交于
-
由 Lee Robinson 提交于
-
- 01 10月, 2020 1 次提交
-
-
- 30 9月, 2020 2 次提交
-
-
由 Philihp Busby 提交于
If this component is missing, an error will be printed to the console ``` Expected Document Component Head was not rendered. Make sure you render them in your custom `_document` See more info here https://err.sh/next.js/missing-document-component ``` Additionally, any components which use CSS modules will fail with an error. This is documented in https://nextjs.org/docs/advanced-features/custom-document
-
由 Amandeep Singh 提交于
-
- 29 9月, 2020 3 次提交
-
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
This handles the case where the children on a head element are undefined and not a string or an array of strings. This doesn't currently handle sub-children on head elements so additional handling will be needed if this is a feature we would like to support although can be discussed/investigated separately from this fix. Fixes: https://github.com/vercel/next.js/issues/17364 Fixes: https://github.com/vercel/next.js/issues/6388 Closes: https://github.com/vercel/next.js/pull/16751
-
- 28 9月, 2020 1 次提交
-
-
由 Tim Feeley 提交于
-
- 26 9月, 2020 2 次提交
-
-
由 JJ Kasper 提交于
-
由 JJ Kasper 提交于
* Expose dotenv loading under separate package * Update pre-compiled * Rename package to @next/env * Update lint ignores * Update package.json Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-
- 25 9月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
Noticed while adding config checks for a new config that the `basePath` checks were wrapped in a `result.experimental` check and even though this should always be true from the default experimental value being an object the `basePath` checks shouldn't be wrapped in this check since it isn't experimental anymore.
-
由 Rishi Raj Jain 提交于
As clear from [#14233](https://github.com/vercel/next.js/pull/14233#issuecomment-645997757) that the 'with-algolia example is not SSR', I've updated the documentation to clear the confusion caused, as visible in #17229 Fixes #17229
-
由 Antonio Pitasi 提交于
Wrong variable was being checked for the hydrate action on redux. This was causing the count to be reset to 0 instead of being 1 when initially loading index.js page. Fixes #17299
-
由 Sam Robbins 提交于
The example has been emptied as it is no longer the recommended way to do it so it shouldn't be linked to
-
- 24 9月, 2020 4 次提交
-
-
由 Sam Poder 提交于
There was a blank line, this PR removes it :D
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Prior to this pull request, Next.js would immediately decode all URLs sent to its server (via `path-match`). This was rarely needed, and Next.js would typically re-encode the incoming request right away (see all the `encodeURIComponent`s removed in PR diff). This adds unnecessary performance overhead. Long term, this will also help prevent weird encoding edge-cases like #10004, #10022, #11371, et al. --- No new tests are necessary for this change because we've extensively tested these edge cases with existing tests. One test was updated to reflect that we skip decoding in a 404 scenario. Let's see if all the existing tests pass!
-
由 Stig Kleppe-Jørgensen 提交于
-
- 23 9月, 2020 1 次提交
-
-
由 Gergo Tolnai 提交于
-
- 22 9月, 2020 6 次提交
-
-
由 Luis Alvarez D 提交于
-
由 Joe Haddad 提交于
-
由 Sébastien Vanvelthem 提交于
Update [`next-auth`](https://github.com/iaincollins/next-auth) from `^2.1.0` to `^3.1.0` and minor sqlite bump to `^5.0.0`.
-
由 Kazuma Furuhashi 提交于
This is a change to add the project name as in the other examples. When we run with the current create command, we are asked for the project name. As follows: ``` $ npx create-next-app --example with-three-js ? What is your project named? › my-app ```
-
由 paulogdm 提交于
This PR removes "vercel.json" from the Yarn workspaces example. Since the release of [monorepos](https://vercel.com/blog/monorepos) support, there is no need to use the "builds" property or "vercel.json".
-
由 Yuji Sugiura 提交于
This PR fixes `info - undefined (N/N)` log for `export` cli. ![image](https://user-images.githubusercontent.com/6259812/93186247-5d801500-f779-11ea-89ec-e20939d7b7c1.png) Default parameter `label` for `createProgress()` was always ignored by `${Log.prefixes.info} undefined`
😅 .
-
- 21 9月, 2020 2 次提交
-
-
由 tomasdisk 提交于
This PR adds an example Next.js project with chakra-ui as its component library using TypeScript. ![image](https://user-images.githubusercontent.com/11686408/91192736-a8ec5980-e6cc-11ea-8f95-b9180defbf47.png) Both libraries has built-in TypeScript declarations. Will help to encourage typed projects, so why not? It's a combination of two existing examples [with-chakra-ui](https://github.com/vercel/next.js/tree/canary/examples/with-chakra-ui) and [with-typescript](https://github.com/vercel/next.js/tree/canary/examples/with-typescript). All credits for their contributors.
-
由 Nghiệp 提交于
* Fix missing yarn.lock * Add --frozen-lockfile flag to speed up install deps * Make sure node_modules do not contains devDependencies * Add --targe stage docker build
-