- 07 Oct, 2020 3 commits
- 06 Oct, 2020 2 commits
-
-
Tantan Fu authored
-
Joe Haddad authored
-
- 05 Oct, 2020 9 commits
-
-
Jashn Maloo authored
Fixes #17200
-
Lee Robinson authored
Addresses remaining comments from https://github.com/vercel/next.js/pull/17491.
-
Lee Robinson authored
Addresses https://github.com/vercel/next.js/issues/17453.
-
JJ Kasper authored
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 authored
Added a test case to make sure that creating a new project within the current directory works as expected.
-
JJ Kasper authored
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 authored
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 authored
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 authored
Fixes #16431 * Added `.babelrc` with `next/babel` to remove the need of the React import on the `with-storybook` example.
-
- 04 Oct, 2020 1 commit
-
-
JJ Kasper authored
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 Oct, 2020 2 commits
-
-
Joris W authored
The page describing exportPathMap goes straight into an example without explaining what the config is for.
-
JJ Kasper authored
Co-authored-by:kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 02 Oct, 2020 4 commits
-
-
Riccardo Di Maio authored
-
Yann Pringault authored
-
JJ Kasper authored
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 authored
-
- 01 Oct, 2020 2 commits
-
-
Lee Robinson authored
-
Luis Alvarez D authored
Fixes https://github.com/vercel/next.js/issues/17505
-
- 30 Sep, 2020 1 commit
-
-
Philihp Busby authored
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
-
- 29 Sep, 2020 2 commits
-
-
Amandeep Singh authored
-
Joe Haddad authored
-
- 28 Sep, 2020 2 commits
-
-
JJ Kasper authored
-
JJ Kasper authored
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
-
- 27 Sep, 2020 1 commit
-
-
Tim Feeley authored
-
- 25 Sep, 2020 4 commits
-
-
JJ Kasper authored
-
JJ Kasper authored
* Expose dotenv loading under separate package * Update pre-compiled * Rename package to @next/env * Update lint ignores * Update package.json Co-authored-by:Joe Haddad <joe.haddad@zeit.co>
-
JJ Kasper authored
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 authored
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
-
- 24 Sep, 2020 5 commits
-
-
Antonio Pitasi authored
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 authored
The example has been emptied as it is no longer the recommended way to do it so it shouldn't be linked to
-
Sam Poder authored
There was a blank line, this PR removes it :D
-
Joe Haddad authored
-
Joe Haddad authored
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!
-
- 23 Sep, 2020 1 commit
-
-
Stig Kleppe-Jørgensen authored
-
- 22 Sep, 2020 1 commit
-
-
Gergo Tolnai authored
-