- 03 Aug, 2020 1 commit
-
-
Joe Haddad authored
-
- 02 Aug, 2020 3 commits
-
-
JJ Kasper authored
Adds additional test cases for cascading env values and corrects behavior Fixes: https://github.com/vercel/next.js/issues/15744
-
sreekumar menon authored
We should remove the dotenv dependency from all Next.js examples (in favor of Next.js environment support): https://github.com/vercel/next.js/issues/15225
-
David Lemayian authored
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.
-
- 01 Aug, 2020 3 commits
-
-
Jan Potoms authored
-
Sam Robbins authored
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/
-
Jan Potoms authored
Fixes https://github.com/vercel/next.js/issues/15755
-
- 31 Jul, 2020 9 commits
-
-
Joe Haddad authored
-
Jan Potoms authored
Irrelevant since https://github.com/vercel/next.js/pull/15379
-
Ronald Stevanus authored
## What The current `gh-pages` example has issue when deploying. This is how the error looks like:  ``` ... 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.
-
Pierre de la Martinière authored
Should prevent some tears when people tries to replicate some example with Next.js 9.5.0 ;) cheers!
-
Rafau authored
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 authored
next-transpile-modules needs to be updated to support Next.js 9.5 Closes #15725
-
Jan Potoms authored
Caught this while reviewing router code for https://github.com/vercel/next.js/pull/15710
-
Luis Alvarez D authored
Fixes https://github.com/vercel/next.js/issues/15719
-
Jan Potoms authored
Saw this one fail on azure
-
- 30 Jul, 2020 13 commits
-
-
JJ Kasper authored
This adds an example of using regex matching for custom routes Fixes https://github.com/vercel/next.js/issues/15712
-
matamatanot authored
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 authored
-
Luis Alvarez D authored
-
Joe Haddad authored
Fixes #15668
-
Arsalan Khattak authored
-
JJ Kasper authored
`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 authored
-
Joe Haddad authored
-
Joe Haddad authored
-
Joe Haddad authored
-
Luis Alvarez D authored
-
Joe Haddad authored
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
-
- 29 Jul, 2020 11 commits
-
-
Stephen Cefali authored
This removes the server 4 example which breaks all server code since the error will happen when the file is sourced.
-
Darsh Patel authored
-
Joe Haddad authored
-
Rafael Almeida authored
-
Jan Potoms authored
-
Joe Haddad authored
-
Jan Potoms authored
Strictly use `basePath` and not `assetPrefix` on `getStaticProps` and `getServerSideProps` Fixes https://github.com/vercel/next.js/issues/15563
-
JJ Kasper authored
-
Luis Alvarez D authored
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 authored
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 authored
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 ) }) ```
-