- 12 11月, 2020 10 次提交
-
-
由 Lucas Varela 提交于
* Add info about SENTRY_URL on source map uploading * Update examples/with-sentry/README.md Co-authored-by: NLee Robinson <me@leerob.io> Co-authored-by: NLuis Alvarez D <luis@vercel.com>
-
由 Vyacheslav Konyshev 提交于
-
## Change - Update package versions - Replace @storybook/addons, @storybook/addon-actions to @storybook/addon-essentials - Replace examples of button, the action function is legacy: https://storybook.js.org/docs/react/essentials/actions#advanced--legacy-usage
-
由 Marco Valsecchi 提交于
Use useRouter over Router and add a workaround for the issue #11639
-
由 JJ Kasper 提交于
This ensures the mixed `notFound`/`redirect` error is shown correctly and adds an err.sh for the error. Closes: https://github.com/vercel/next.js/issues/18727
-
由 JJ Kasper 提交于
This fixes a few things related to optional catch-all routes and i18n. The first thing is it ensures the correct data route is generated on the client so that the locale isn't duplicated for an optional catch-all route, the next is it ensures the browser history is updated correctly when only a locale change is occurring, and then it also ensures we handle the locales and normalizing for fallback optional catch-all pages correctly. Tests have been added to ensure these cases are covered properly and we don't regress on them, these changes were also tested on Vercel [here](https://next-js-bug-i18n-root-params-nybg44l0b.vercel.app/) Fixes: https://github.com/vercel/next.js/issues/18633 Fixes: https://github.com/vercel/next.js/issues/19059
-
由 Daniel Stocks 提交于
Added `<Html>` and `<Head>` components in the custom `_document.js` for the with-fela example package This fixes an issue where fela `<style>` tags were not added and sent as part of the server-side rendered HTML payload, causing a FOUC.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
This pull request completely replaces our old page loader with a brand new route loader. Our existing comprehensive test suite means I did not need to add a bunch of tests. I did add them where behavior was added or fixed. Summary of the changes: - Eagerly evaluates prefetched pages in browser idle time (speeds up transitions) - Router is **no longer frozen** indefinitely if the Build Manifest never arrives - Router is **no longer frozen** indefinitely if a page fails to bootstrap - New `withFuture` utility instead of ad-hoc deduping per resource - Prefetching is now delayed until browser idle time to not impact TTI - Browsers without `prefetch` now fall back to eager evaluation instead of using `preload` - We're now ready to serve non-static assets **with `no-store` without breaking prefetching** - **Application can now hydrate without fetching CSS assets—this is a huge performance win that was previously blocking hydration** --- The minor size increase here is unfortunate, but we have to incur it for correctness. --- Fixes #18389 Fixes #18642
-
由 JJ Kasper 提交于
-
- 11 11月, 2020 17 次提交
-
-
由 Steven 提交于
Fixes #18356
-
由 Kristoffer K 提交于
**What's the problem this PR addresses?** https://github.com/vercel/next.js/pull/18768 started to ncc `@babel/plugin-transform-runtime` which broke its Yarn PnP support since the version of `resolve` it uses can't be patched by Yarn. Fixes https://github.com/yarnpkg/berry/runs/1359235077?check_suite_focus=true#step:5:79 cc @guybedford **How did you fix it?** Resolve the absolute path to `@babel/runtime` so it doesn't have to go through `resolve` --- Fixes https://github.com/vercel/next.js/issues/19026
-
由 Daniel K 提交于
This confused me a lot, because in the case of `withBundleAnalyzer({})` it will ignore any previous config and basically override everything. Furthermore, it makes more sense to move the call with `enabled` option inside so it's aligned with other plugins approach. -
由 JJ Kasper 提交于
Updates to the latest version of `chokidar` x-ref: https://github.com/vercel/next.js/issues/17416
-
由 JJ Kasper 提交于
This ensures we match the `basePath` handling for redirects in `next.config.js` with redirects from `getStaticProps` and `getServerSideProps` and also adds a separate test suite to ensure GS(S)P redirects with `basePath` work correctly Fixes: https://github.com/vercel/next.js/issues/18984 Closes: https://github.com/vercel/next.js/pull/18892
-
由 JJ Kasper 提交于
This ensures we use the `defaultLocale` for a locale domain when rendering non-static pages. Static pages will initially contain the global `defaultLocale` and then be updated on the client since we don't currently prerender a version of the pages for each locale domain. Closes: https://github.com/vercel/next.js/issues/18970
-
由 Kanitkorn Sujautra 提交于
In `with-typescript-eslint-jest` example, `identity-obj-proxy` is being used here, but it's not in `package.json` yet. https://github.com/vercel/next.js/blob/5b1be2bb980c4cad7e543a9f150c1a1c50a6c0f3/examples/with-typescript-eslint-jest/jest.config.js#L14 This PR adds `identity-obj-proxy` to `package.json`.
-
由 Lyderic Dutillieux 提交于
Changed function name from "getStaticProps" to "getStaticPaths" in Exception message thrown when 'paths' is invalid.
-
由 Ante Sepic 提交于
If the example is cloned and ran with no further setup (no environment variables set up), it will error out because `extractPostEntries` will return `undefined` which can not be serialized by `getStaticProps `. This PR basically ensures that we return an empty array instead of the `undefined` for a collection of posts, and a `null` instead of the `undefined` for a single post.
-
由 Callum Booth 提交于
Helps with https://github.com/pmndrs/zustand/issues/182 I have seen the comments from this PR https://github.com/vercel/next.js/pull/11222#pullrequestreview-406998918 and this PR matches the with-redux example.
-
由 Ash Connell 提交于
* Add with-knex example * Fix with-knex README typo Co-authored-by: NAsh Connell <hello@ashconnell.com> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Joe Haddad 提交于
-
由 Gerald Monaco 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co> -
由 WeichienHung 提交于
Fixes https://github.com/vercel/next.js/issues/16550 Add a graphql mutation operation in this example. The changes are: 1. Define mutation in schema `type-defs.graphqls` 2. Add mutation to `viewer.graphql ` that compiled to typescript code. 3. Add mutation resolver in `resolvers.ts` 4. [UI] add a input box and button to submit mutation request to change name. screenshot of change 
-
由 Steven 提交于
We fixed this in a previous PR but there were no tests for `.ico` so this PR adds a test for it to ensure we don't regress. Similar to SVG, we bypass ICO because it typically contains multiple sizes in a single file. Closes #18600
-
由 JJ Kasper 提交于
-
由 Steven 提交于
This PR moves the `<a>` element inside the `<svg>` element.
-
- 10 11月, 2020 6 次提交
-
-
由 Joe Haddad 提交于
-
由 Steven 提交于
Fixes #18563 by adding the etag header to the optimized image response. This does _not_ change the expireAt (TTL) for cached files on the server, which still uses the max-age of the upstream response. The new file format on disk for cached image files is the following: ``` .next/cache/images/<HASHED_QUERYSTRING>/<EXPIREAT>.<ETAG>.<EXT> ```
-
由 David Golden 提交于
upgrade mobx dependencies for with-mobx example and make all necessary code changes as per https://mobx.js.org/migrating-from-4-or-5.html addresses #17809
-
由 Galanggg 提交于
This PR adds an example Next.js project with GSAP 
-
由 Joe Haddad 提交于
-
由 Weston Thayer 提交于
## New features - Example of how to use `Sentry.captureException()` in API routes https://github.com/vercel/next.js/commit/5a35982717bc7f916022dd713b3b1f9e0921d503 ## Bug fixes - Server-side source maps now work in Sentry when deployed to Vercel https://github.com/vercel/next.js/commit/629a9ed5048629dc12670ef457fe6efaa2e8d3b6 - If uploading source maps, `Sentry.init()` now sets the `release`, so that exceptions are correctly associated with the source maps in that release ## Open issues ### `_error.js` is unused for `getServerSideProps` errors when deployed to Vercel Instead of rendering this example's overridden `_error.js` (like it does when testing locally with `NODE_ENV='production'`), when deployed to Vercel and an Error is thrown from `getServerSideProps`, this page is shown:  This confuses me because the Error is still successfully sent to Sentry, but I would've expected it to be sent by the call to `Sentry.captureException()` in `_error.js`. I'm not sure why it works. ### API test 2 & 3 don't work in the "server" build config They don't work when deployed to Vercel in the "serverless" config either, but that's expected because there aren't any handlers to flush the Sentry queue. I can't figure out why they don't work in the long-lived "server" config.
-
- 09 11月, 2020 7 次提交
-
-
由 iczero 提交于
`node-sass` v5 introduced support for Node.js v15, which is not supported by v4. However, Next.js currently errors with ``` Error: Node Sass version 5.0.0 is incompatible with ^4.0.0. ``` when attempting to build with `node-sass` 5.0.0. This error comes from `sass-loader`. They have recently released version 10.0.5 which supports `node-sass` 5.0.0 (PR <https://github.com/webpack-contrib/sass-loader/pull/899>, release <https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.5>).
-
由 tolfino 提交于
This replaces the seen set with a newly instantiated map of refs per value in the array. This corrects the behavior that the refs map passed into isSerializable contains only values along the path to the current value: previously, because the refs map was shared among all values in the array, this would trigger on instances such as: ```js const x = []; isSerializableProps('/', 'test', { arr: [x, [x]] }); ``` ... where the reference is shared but there is no cycle formed, as the presence of elements is disjoint. Fixes #18228. -
由 James George 提交于
Prevent `catch` assertions in tests.
-
由 Davidson Nascimento 提交于
- Changed script `start` to `dev` and improved it #18934 adding commando to transpile electron code; - Added some folders into `.gitignore`; - Updated react to avoid issues as #18916 Fixes #18934
-
由 JJ Kasper 提交于
This updates to use the `Build.SourceVersion` value from the [predefined variables](https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml) for the cache key instead of the pull request value since it isn't available after merging to canary. x-ref: https://github.com/vercel/next.js/pull/18931
-
由 Tadao Iseki 提交于
This allows to import the type `ImageProps` from `next/image` like `next/link`. https://github.com/vercel/next.js/blob/a6660729ea82fbcb26cfe7c89637b1af37255c9f/packages/next/client/link.tsx#L21 ## Usage ```tsx import Image, { ImageProps } from 'next/image' const CustomImage: React.FC<ImageProps> = (props) => ( <Image {...props} unsized /> ) ```
-
由 JJ Kasper 提交于
-