- 31 7月, 2020 7 次提交
-
-
由 Jon Espen Kvisler 提交于
next-transpile-modules needs to be updated to support Next.js 9.5 Closes #15725
-
由 Jan Potoms 提交于
Caught this while reviewing router code for https://github.com/vercel/next.js/pull/15710
-
-
由 Jan Potoms 提交于
Saw this one fail on azure
-
由 JJ Kasper 提交于
This adds an example of using regex matching for custom routes Fixes https://github.com/vercel/next.js/issues/15712
-
由 matamatanot 提交于
You have been redirected to the`/home` page. I'm not sure if that's correct, but it's been fixed to move the link to the document. https://vercel.com/smart-cdn https://vercel.com/docs/v2/edge-network/overview
-
由 Luis Alvarez D 提交于
-
- 30 7月, 2020 17 次提交
-
-
由 Luis Alvarez D 提交于
-
由 Joe Haddad 提交于
Fixes #15668
-
由 Arsalan Khattak 提交于
-
由 JJ Kasper 提交于
`pageProps` should always be defined to ensure everything is working as expected although to prevent a breaking change this adds an additional check before attempting to access `pageProps` before hydration. It also adds tests to prevent regressing on this Closes: https://github.com/vercel/next.js/issues/15647
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Luis Alvarez D 提交于
-
由 Joe Haddad 提交于
This pull request: 1. Relocates tests to correct location 1. Tests more scenarios 1. Fixes a bug with anchors at the start of error message 1. Fixes react key warning error Fixes #15599
-
由 Stephen Cefali 提交于
This removes the server 4 example which breaks all server code since the error will happen when the file is sourced.
-
由 Darsh Patel 提交于
-
由 Joe Haddad 提交于
-
由 Rafael Almeida 提交于
-
由 Jan Potoms 提交于
-
由 Joe Haddad 提交于
-
由 Jan Potoms 提交于
Strictly use `basePath` and not `assetPrefix` on `getStaticProps` and `getServerSideProps` Fixes https://github.com/vercel/next.js/issues/15563
-
- 29 7月, 2020 12 次提交
-
-
由 JJ Kasper 提交于
-
由 Luis Alvarez D 提交于
Fixes https://github.com/vercel/next.js/issues/15595 - Updated the tailwindcss and tailwindcss-emotion examples to the latest version of tailwindcss - Added a new `with-styled-jsx` example - Updated the `basic-css` example to use CSS Modules instead of styled-jsx - Added the examples to the documentation page for built-in css support
-
由 JJ Kasper 提交于
This updates collecting dynamic route params on Vercel to make sure that missing optional dynamic routes are undefined. Additional tests for this mode have also been added to ensure the params are being collected properly Closes: https://github.com/vercel/next.js/issues/15579
-
由 Jan Potoms 提交于
errors in script execution will result in timeout instead of failure. This PR makes sure to pass all arguments to `.then` so error handling is correctly set up. (`.then` needs to be able to take a second argument). I also removed `.finally`. I don't know why, but it looks like the following test does something that prevents the tests after it from opening a new browser window on azure. I'm giving up, I shuffled the tests to put this one last. ```js it('shows warning when dynamic route mismatch is used on Link', async () => { await showsError( '/dynamic-route-mismatch', /Mismatching `as` and `href` failed to manually provide the params: post in the `href`'s `query`/, true, true ) }) ```
-
由 JJ Kasper 提交于
This adds a note to our documentation about the `statusCode` config to match the note from the redirects documentation for [`vercel.json`](https://vercel.com/docs/configuration#project/redirects)
-
由 JJ Kasper 提交于
Instead of trying to parse header values as URLs and then replace path segments in them this switches to escaping characters that can break `path-to-regexp` compiling Fixes: https://github.com/vercel/next.js/issues/15580 x-ref: https://github.com/vercel/vercel/pull/4942
-
由 yokinist 提交于
-
由 Robert van Steen 提交于
-
由 JJ Kasper 提交于
This ensures rendering `next/link` doesn't fail without being nested under the router context. Closes: https://github.com/vercel/next.js/issues/15543
-
由 JJ Kasper 提交于
This attempts to stabilize the `error-is-clickable` test since it has been flaking recently Closes: https://github.com/vercel/next.js/issues/15585
-
由 laiso 提交于
It seems like the error occurs with `next export` when building the current example. ``` $ cd examples/with-electron-typescript $ yarn && yarn build Error occurred prerendering page "/detail". Read more: https://err.sh/next.js/prerender-error Error: Error for page /detail: pages with `getServerSideProps` can not be exported. See more info here: https://err.sh/next.js/gssp-export Error: Export encountered errors on following paths: /detail at exportApp (/Users/kstg/src/github.com/zeit/next.js/examples/with-electron-typescript/node_modules/next/dist/export/index.js:22:1166) error Command failed with exit code 1. ``` I changed routes to statically resolve pages generating from `pages/detail.tsx` and added `getStaticPaths` and `getStaticProps`. so then it will export as follows ``` yarn run v1.22.4 $ next build renderer && next export renderer Creating an optimized production build... Compiled successfully. Automatically optimizing pages... Page Size First Load JS ┌ ○ / 336 B 62.6 kB ├ ○ /404 2.54 kB 61.6 kB ├ ○ /about 338 B 62.6 kB ├ ● /detail/[id] 440 B 62.7 kB ├ ├ /detail/101 ├ ├ /detail/102 ├ ├ /detail/103 ├ └ /detail/104 └ ● /initial-props 530 B 62.8 kB + First Load JS shared by all 59.1 kB ├ static/pages/_app.js 983 B ├ chunks/commons.9facbe.js 10.9 kB ├ chunks/framework.b76773.js 40.3 kB ├ runtime/main.800476.js 6.22 kB └ runtime/webpack.c21266.js 746 B λ (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps) ○ (Static) automatically rendered as static HTML (uses no initial props) ● (SSG) automatically generated as static HTML + JSON (uses getStaticProps) > using build directory: /Users/kstg/src/github.com/zeit/next.js/examples/with-electron-typescript/renderer/.next copying "static build" directory > No "exportPathMap" found in "next.config.js". Generating map from "./pages" launching 7 workers Exporting (0/4) Exporting (1/4) Exporting (2/4) Exporting (3/4) Exporting (4/4) Export successful Done in 11.47s. ```
-
(p.s. excited to use this package. thank you.)
-
- 28 7月, 2020 4 次提交
-
-
由 JJ Kasper 提交于
This makes sure to not group the polyfills chunk in with the client bundles group now that it is output under chunks instead of runtime
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Rafael Almeida 提交于
* Add release hook * Remove release.js exported config * Add skip flag to release CLI * Use full flag name * Upgrade release * Update yarn.lock Co-authored-by: NTim Neutkens <timneutkens@me.com>
-