- 02 8月, 2020 2 次提交
-
-
由 David Lemayian 提交于
Thank you for the excellent examples. This PR updates the `.gitignore` for [with-electron](https://github.com/vercel/next.js/tree/canary/examples/with-electron) example to ignore the output folders.
-
由 Jan Potoms 提交于
-
- 01 8月, 2020 5 次提交
-
-
由 Sam Robbins 提交于
While it is mentioned in the [link documentation](https://nextjs.org/docs/api-reference/next/link), I think it is useful to also explain in the dynamic route documentation that you need to include the as parameter when routing to a dynamic route/
-
-
由 Joe Haddad 提交于
-
由 Jan Potoms 提交于
Irrelevant since https://github.com/vercel/next.js/pull/15379
-
由 Ronald Stevanus 提交于
## What The current `gh-pages` example has issue when deploying. This is how the error looks like: ![image](https://user-images.githubusercontent.com/1008093/88996697-827f0c80-d320-11ea-93bd-48141c321a65.png) ``` ... Export successful The following paths are ignored by one of your .gitignore files: out hint: Use -f if you really want to add them. hint: Turn this message off by running hint: "git config advice.addIgnoredFile false" npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! next@1.0.0 deploy: `rm -rf node_modules/.cache && next build && next export && touch out/.nojekyll && git add out/` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the next@1.0.0 deploy script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: ... ``` It's because `out` folder is added on `.gitignore` and the deploy script runs `git add out/`. The fix is to remove `out` folder from `.gitignore`. ## How was it tested run `npm run deploy`, it should be completed successfully.
-
- 31 7月, 2020 9 次提交
-
-
由 Pierre de la Martinière 提交于
Should prevent some tears when people tries to replicate some example with Next.js 9.5.0 ;) cheers!
-
由 Rafau 提交于
I think this is necessary for IE11. via [Webpack docs](https://webpack.js.org/migrate/5/#turn-off-es2015-syntax-in-runtime-code-if-necessary) > By default, webpack's runtime code uses ES2015 syntax to build smaller bundles. If your build targets environments that don't support this syntax (like IE11), you'll need to set output.ecmaVersion: 5 to revert to ES5 syntax. Thank you
-
由 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 7 次提交
-
-
由 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 提交于
-