- 06 Jan, 2021 19 commits
-
-
Joe Haddad authored
-
Joe Haddad authored
-
Simon Taggart authored
* feat: add Twilio Paste example * Updated readme Co-authored-by:
Luis Alvarez <luis@vercel.com> Co-authored-by:
kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
Bar authored
-
Joe Haddad authored
-
Shu Uesugi authored
Rename https://next-blog-starter.now.sh to https://next-blog-starter.vercel.app (@lfades renamed the domain name)
-
David ALLIX authored
Follow https://github.com/vercel/next.js/pull/20628
-
Sebastian König authored
* 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:
Sebastian König <sebastian_koenig@cotyinc.com> Co-authored-by:
Luis Alvarez D <luis@vercel.com>
-
Joe Haddad authored
-
Farhan Ullah authored
-
Damien Varron authored
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.
-
Michael Aufreiter authored
-
Tim Neutkens authored
Fixes #20403
-
JJ Kasper authored
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 authored
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 authored
Fix mini typo
-
Lee Robinson authored
Docs for https://github.com/vercel/next.js/pull/20216/.
-
Joe Haddad authored
-
JJ Kasper authored
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
-
- 05 Jan, 2021 11 commits
-
-
Josh authored
* Updated deploy button URL * Update bottom button
-
Thomas Wang authored
You can initialize the Firebase app instance without checking for window, but it is required for using the analytics module.
-
Alex Castle authored
This is a #19325 reconfigured to support a loader passed in via a `loader` prop on the Image component, rather than using a config-based approach. The idea is that applications wanting to use a custom loader will create a wrapper element for the image component that incorporates that loader. See a simple example of this pattern in the integration tests. This solution is similar to the one prototyped by @ricokahler in #20213 and described at https://github.com/vercel/next.js/issues/18606#issuecomment-720149156 --- Closes #19325 Fixes #18606
-
kaykdm authored
Co-authored-by:Kanta Kodama <kanta.kodama@linecorp.com>
-
Tom authored
-
Tom authored
-
tarunama authored
## summary - Explicitly define return types - Add type of [Observer](https://github.com/vercel/next.js/pull/20728/files#diff-5de64b97b2f26e4e41d197a8295e8750825c75b8ca557a4b947a4c3569345974R7)
-
JJ Kasper authored
Closes: https://github.com/vercel/next.js/issues/20197
-
Tuan Nguyen authored
`getLoginSession` takes only one argument
-
Tim Neutkens authored
-
JJ Kasper authored
Adds the `pr` section from https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#pr-triggers to filter paths that don't require test runs on PRs.
-
- 04 Jan, 2021 10 commits
-
-
Jan Varho authored
Currently pages with `notFound: false` from `getServerSideProps` behave the same as `notFound: true`, i.e. just having the key is enough to result in a 404. This fixes the check in render.tsx and adds tests for it.
-
Lee Robinson authored
Adds an example using `lru-cache` to implement a simple rate limiter for API routes ([Serverless Functions](https://vercel.com/docs/serverless-functions/introduction)). **Demo: https://nextjs-rate-limit.vercel.app/**
-
Jesse Jafa authored
Closes https://github.com/vercel/next.js/issues/19481 The current text implies `query` is a string. IMO it would be better if it clarified that `query` is an object containing the query string's keys and values Edit: Relevant docs url: https://nextjs.org/docs/basic-features/data-fetching#getserversideprops-server-side-rendering
-
zoomdong authored
https://ant.design/docs/react/getting-started#Import-on-Demand At the document, We don't need to use `babel-import-plugin` to `Import on Demand`.
-
Manaia Junior authored
-
Justin Philpott authored
Hi, I'm submitting this PR for consideration as a new example app showing Styled JSX with SCSS working inside and outside storybook with example components. Only known issue: I noticed that when running this example with: `$ yarn next ./examples/with-storybook-styled-jsx-scss` I receive the following error: ``` error - ./pages/_app.js Error: [BABEL] .../next.js/examples/with-storybook-styled-jsx-scss/pages/_app.js: Cannot find module 'styled-jsx-plugin-sass' (While processing: ".../next.js/node_modules/next/babel.js") ``` However I notice that this same missing module error is triggered when running this existing example app "with-styled-jsx-scss". Any changes/tweaks needed? Thanks!
-
mongolyy authored
I made the following changes. - Addition of procedure for setting private_key - Addition of procedure for creating a database and setting database_url
-
Joe Haddad authored
This pull request correctly assigns boolean attributes for `<script />` to match the element as it is created by a server-side render. Prior to this pull request, we'd double-execute `<script>` tags with the `async`, `defer`, or `nomodule` property. --- Fixes #9070
-
matamatanot authored
As with `const width`, it should be declared just before it is used.
-
Kristoffer K authored
**What's the problem this PR addresses?** `@next/mdx` adds the webpack loader `@mdx-js/loader` without resolving it to an absolute path Depends on https://github.com/vercel/next.js/pull/17606 **How did you fix it?** `require.resolve` the webpack loader before adding it
-