- 12 6月, 2020 11 次提交
-
-
由 Matthew Sweeney 提交于
This PR updates the `with-userbase` example with the following changes: - Removes the `vercel.json` file, this is no longer needed with [recent changes](https://vercel.com/docs/v2/build-step#environment-variables). - Changes the URL of the Deploy Button to use `?env`, `?envLink`, and `?envDescription` query strings, these prompt for environment variables upon import. - Updates the instructions to reflect the changes made to the import and deployment process.
-
由 Jason Miller 提交于
Should fix https://github.com/vercel/next.js/pull/13976#issuecomment-641677695 /cc @monsonjeremy - let me know if this work for you.
-
由 Luis Alvarez D 提交于
[ch2502] - Added new import flow to every CMS example, using the deploy button, and removed `vercel.json` - Replaced `dotenv` with the new env support in outdated examples
-
由 Tim Neutkens 提交于
Fixes #9326
-
由 Sebastian Benz 提交于
This addresses the problem of the optimizer postinstall hook causing delayed installs if run behind a proxy. See https://github.com/ampproject/amp-toolbox/issues/832 Fixes #14070
-
由 Joe Haddad 提交于
Fixes #14093
-
由 HYUNSANG HAN 提交于
Links of the example about `custom-server-koa` were wrong, so I fixed them.
-
由 Joe Haddad 提交于
Fixes #14085
-
由 Todor Totev 提交于
Related to [11014](https://github.com/vercel/next.js/issues/11014)
-
由 Todor Totev 提交于
Related to [11014](https://github.com/vercel/next.js/issues/11014)
-
由 JJ Kasper 提交于
This adds a test case to ensure hard navigating when a client bundle fails to load is occurring correctly x-ref: https://github.com/vercel/next.js/issues/13516
-
- 11 6月, 2020 14 次提交
-
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 JJ Kasper 提交于
To make `asPath` consistent with `basePath` handling this makes sure it is always stripped including on the client under the `asPath` value and from `req.url` in the `serverless-loader`. Additional tests have been added for this behavior to ensure we don't regress on this Closes: https://github.com/vercel/next.js/issues/14037 Closes: https://github.com/vercel/next.js/issues/14039
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
Co-authored-by: NJJ Kasper <jj@jjsweb.site> Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Cristian 提交于
* [Examples] Update with-chakra-ui * Pass theme prop to ThemeProvider Co-authored-by: NCristian Dominguez <cristiand391@users.noreply.github.com>
-
由 Shu Uesugi 提交于
[ch2842] - Demo: https://next-blog-storyblok.now.sh/ - Preview Mode: https://next-blog-storyblok.now.sh/api/preview?secret=5nnybHTKlbzkOa6r&slug=draft-post-test
-
由 Jason Merino 提交于
-
由 Mohamed SADAT 提交于
Hello
👋 This PR is to replace styled-jsx by Global CSS and CSS modules in the default Next.js template according to the issue [#13965](https://github.com/vercel/next.js/issues/13965) opened by @Timer -
由 Joe Haddad 提交于
This builds off of @timneutkens's PR instead of updating it because it's his `canary` branch. Updated to still `stat`, as it's the only way to test the difference between a file and directory. --- Closes #13506 Fixes #12235
-
由 Joe Haddad 提交于
Fixes #13978
-
由 JJ Kasper 提交于
This correctly strips the `basePath` before generating the `route-matcher` for dynamic routes and adds regression tests to ensure these work correctly with the `basePath` feature Closes: https://github.com/vercel/next.js/issues/13966
-
由 Shu Uesugi 提交于
[ch2580] **Demo:** https://next-blog-buttercms.now.sh/ **Preview Mode:** https://next-blog-buttercms.now.sh/api/preview?secret=CdEAKMRT4tAwzqiD&slug=draft-post-test
-
由 JJ Kasper 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
- 10 6月, 2020 15 次提交
-
-
由 stefanprobst 提交于
allow extending the recommended eslint-plugin-next config, without having to specify the plugin name in the plugins array. eslint does not do this automatically, see the note [here](https://eslint.org/docs/developer-guide/working-with-plugins#configs-in-plugins)
-
由 Ben Spinks 提交于
Hi, This PR inverts the colors for the compiling indicator, closes #13952. The second commit makes the styling consistent with the prerender indicator (height and border) From: ![before](https://user-images.githubusercontent.com/32001471/84236653-df640080-aaef-11ea-8532-a5d65cab5cc3.gif) To: ![after](https://user-images.githubusercontent.com/32001471/84247287-c6fbe200-aaff-11ea-9eff-a16c42a7b625.gif)
-
由 Darsh Patel 提交于
```.next``` folder wasn't in the gitignore file causing .next folder to be tracked by git
-
由 Dylan Jhaveri 提交于
* function rename * update package.json dependencies to use `^` for semver. I noticed the package-lock.json is not committed in these examples, which seems to be intentional. Is it advisable to use semver for dependencies? This could actually break if someone clones, installs and a newer version of something has a breakage, but in general it might be nice to have folks installing the latest patch releases for deps. * use Upchunk 2.0.0. with 1000x [better progress reporting on uploads](https://github.com/muxinc/upchunk/releases/tag/v2.0.0) **Notice the progress %** Upchunk pre 2.0: ![before-loading](https://user-images.githubusercontent.com/764988/84232581-70fa5080-aaa5-11ea-8db8-2cfe50339b43.gif) Upchunk 2.0: ![after-loading](https://user-images.githubusercontent.com/764988/84232620-85d6e400-aaa5-11ea-82cc-b348ead1f5de.gif)
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
Webpack will randomly execute script order if its runtime is not prioritized before chunks execute. This seems to be somehow triggered in #13870 because of slightly different script ordering. This had actually broke CSS, which is why our tests are failing 50% of the time: Without this PR: ![image](https://user-images.githubusercontent.com/616428/84221491-57f0a000-aaa3-11ea-9dff-c27c87d29ac5.png) However, it's still problematic to use `async` in development since we rely on script execution order. So, this PR disables `async` in development. We're exploring `defer` in the future anyway (over `async`), which will be ordered, so I don't mind diverging between dev and prod in this way. --- Fixes #13911
-
由 Luis Alvarez D 提交于
Related to https://github.com/vercel/next.js/issues/11014
-
由 Luis Alvarez D 提交于
Related to https://github.com/vercel/next.js/issues/11014 The authentication method has been replaced with an improved version of the passport example.
-
由 James Mosier 提交于
Sorry for the super trivial PR. I noticed this while working with the example and figured it might be worth fixing.
-
由 James Mosier 提交于
If a user does not specify `--example` when using create-next-app then just spin up the default template and only prompt them for the name of their project. if a user does specify `--example` (with no string after it) then show them the example picker. Closes #13960
-
-
由 JJ Kasper 提交于
This adds scroll restoration handling to make sure the correct scroll position is restored after navigating back/forward to a page and the rendering hasn't completed by the time the default browser scroll restoration has taken place. An initial failing test case was added which is working with the changes in this PR, if there are any other cases that should be added let me know and I can make sure we have them to ensure we don't regress on this behavior --- Fixes #12530
-
由 Jason Miller 提交于
This adds [prefresh](https://github.com/JoviDeCroock/prefresh) and [preact/debug + DevTools](https://preactjs.com/guide/v10/debugging/) during development. It also fixes the chunking/splitting configuration for production builds by creating a `preact` chunk based on the existing framework chunk. I'm still considering publishing the config here as a plugin, since I worry about the copy-paste effect on this much regex-foo. /cc @jovidecroock
-
由 Jan Potoms 提交于
Extracted from https://github.com/vercel/next.js/pull/13333, the same exact code lives in that PR as well, but we can merge this separately if it makes reviewing https://github.com/vercel/next.js/pull/13333 easier This PR does 3 things - deduplicate code from build and next-dev-server that loads custom routes from next.config.js (`loadCustomRoutes`) - in `loadCustomRoutes`, load these rewrites, headers and redirects configs concurrently instead of sequentially. - in next-server, make `this.customRoutes` always defined, this allows us to remove the big `if` around its initialization code in `generateRoutes`, which in turn makes it possible to reuse this code for other routing than user defined routes, which is how https://github.com/vercel/next.js/pull/13333 adds its redirects.
-
由 Joe Haddad 提交于
Fixes #13972
-