- 11 1月, 2021 13 次提交
-
-
由 Ludovico Fischer 提交于
Fixes #20474 * Switch API url to working URL used in apollo example * Update deps * Move styled jsx out of the way to avoid demonstrating too many unfamiliar concepts at once dev, build and start work now.
-
由 Tim Neutkens 提交于
Fixes #20408 Fixes #20925
-
由 Vlad Frolov 提交于
I have not bumped into any bug, I was just playing around https://lgtm.com/projects/g/vercel/next.js/, and this looked like a legit suggestion to fix
-
由 Almad 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl>
-
由 Hyeon Kim (김지현) 提交于
Prevent unpredictable dependency hosting by explicitly resolve module path on webpack.ProvidePlugin (#20971) ProvidePlugin replaces certain identifiers with another modules. As a result, 'buffer' and 'process' modules are added as implicit dependencies to all Next.js plugins. This can be problematic. With "Plug'n'Play" strategy, it don't work at all since they fail-fast with implicit dependencies. With "node_modules" strategy, it might seem OK but actually it can be result into unpredictable behavior since in uses dependency [hoisting](https://yarnpkg.com/advanced/lexicon#hoisting). For example, currently users cannot use next-auth plugin with Plug'n'Play strategy: ![image](https://user-images.githubusercontent.com/4435445/103481517-d5547700-4e1e-11eb-9f23-bc2c9939418e.png) This patch let Next.js properly handles such cases with `require.resolve`. Closes https://github.com/vercel/next.js/issues/20955 ###### References: - https://github.com/nextauthjs/next-auth/pull/1034
-
由 Lachlan Campbell 提交于
Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: NTim Neutkens <timneutkens@me.com>
-
由 Tim Neutkens 提交于
Fixes #20887
-
由 Tom 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Tom 提交于
-
由 taisei mima 提交于
-
由 Michael McQuade 提交于
-
由 Michael McQuade 提交于
-
由 Victor Assis 提交于
-
- 10 1月, 2021 1 次提交
-
-
由 Tim Neutkens 提交于
-
- 08 1月, 2021 3 次提交
-
-
由 JJ Kasper 提交于
This adds retrying for getting redbox content and ensures the `next.config.js` file is cleaned up for the dynamic-routing test suite. x-ref: https://github.com/vercel/next.js/pull/20786#issuecomment-755929891
-
由 Daniel Stumme 提交于
This single sentence addition would have saved me about a day of troubleshooting. This doc doesn't mention how the inline occurs. The only place I could eventually find that mentions this is the server & public runtime config pages.
-
- 07 1月, 2021 15 次提交
-
-
由 tarunama 提交于
## summary - add return types - move `locale` variable const from let - ~use [strict equality](https://github.com/vercel/next.js/pull/20806/files#diff-2433946f9a058f1b070138d12c20f10a9128e46408033629181f9f7fc3b9b9b2R275)~
-
由 Luc Leray 提交于
-
由 Jeremy Balog 提交于
-
由 Luc Leray 提交于
Fix all deploy button URLs in the Next.js repo to follow the following format: ``` https://vercel.com/new/git/external?repository-url=https://github.com/vercel/next.js/tree/canary/examples/<EXAMPLE_NAME>&project-name=<EXAMPLE_NAME>&repository-name=<EXAMPLE_NAME> ``` The detailed docs for the Deploy Button can be found here: https://vercel.com/docs/more/deploy-button. Also updates legacy Vercel import flow URLs (starting with vercel.com/import or with vercel.com/new/project), to use the new vercel.com/new URLs. --- For example, for the `hello-world` example: The URL is https://vercel.com/new/git/external?repository-url=https://github.com/vercel/next.js/tree/canary/examples/hello-world&project-name=hello-world&repository-name=hello-world And the deploy button looks like this: [![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/git/external?repository-url=https://github.com/vercel/next.js/tree/canary/examples/hello-world&project-name=hello-world&repository-name=hello-world) --- For reference, I used the following regexes to search for the incorrect URLs ``` \(https://vercel.com/import/git\?s=https://github.com/vercel/next.js/tree/canary/examples/(.*)\) \(https://vercel.com/import/git\?c=1&s=https://github.com/vercel/next.js/tree/canary/examples/([^&]*)(.*)\) \(https://vercel.com/import/project\?template=https://github.com/vercel/next.js/tree/canary/examples/(.*)\) https://vercel.com/import/git https://vercel.com/import/select-scope https://vercel.com/import https://vercel.com/new/project ```
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Simon Taggart 提交于
* feat: add Twilio Paste example * Updated readme Co-authored-by: NLuis Alvarez <luis@vercel.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Bar 提交于
-
由 Joe Haddad 提交于
-
由 Shu Uesugi 提交于
Rename https://next-blog-starter.now.sh to https://next-blog-starter.vercel.app (@lfades renamed the domain name)
-
由 David ALLIX 提交于
Follow https://github.com/vercel/next.js/pull/20628
-
由 Sebastian König 提交于
* Added with-mqtt-js example * Fixed eslint/prettier errors * Update README.md * Updated with-mqtt-js to latest next/react versions, WIP: Refactoring useMqtt() * A2PC * Working example, unrefactored * A2PC * Ran prettier * Used NEXT_PUBLIC_ prefix instead of keys as props * Updated readme and added .env.local.example Co-authored-by: NSebastian König <sebastian_koenig@cotyinc.com> Co-authored-by: NLuis Alvarez D <luis@vercel.com>
-
由 Joe Haddad 提交于
-
由 Farhan Ullah 提交于
-
由 Damien Varron 提交于
Fixes #16864 The `router` can be missing in a test environment when trying to render a `Link` component. This PR bails out of `router.prefetch()` when `router` is missing. The alternative is for users to mock `next/link` or to mock the `router` and wrap their test components. Please let me know any feedback.
-
- 06 1月, 2021 8 次提交
-
-
由 Michael Aufreiter 提交于
-
由 Tim Neutkens 提交于
Fixes #20403
-
由 JJ Kasper 提交于
This updates the error shown when a path doesn't match the dynamic route in `getStaticPaths` to not include the `locale` since this isn't considered when matching against the dynamic route.
-
由 JJ Kasper 提交于
This ensures rewrites to API routes with i18n enabled handles as an API route correctly. This also adds tests for API routes in the i18n test suite Fixes: https://github.com/vercel/next.js/issues/20725
-
由 Benjamin Bender 提交于
Fix mini typo
-
由 Lee Robinson 提交于
Docs for https://github.com/vercel/next.js/pull/20216/.
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
This is a follow-up to https://github.com/vercel/next.js/pull/20596 and https://github.com/vercel/next.js/pull/20658 ensuring the `as` value is prefixed with the `basePath` correctly with a query. This updates the test to also ensure no errors are shown when a query is present on the index `basePath` route. Fixes: https://github.com/vercel/next.js/pull/20757#issuecomment-754338510
-