- 31 5月, 2020 4 次提交
-
-
由 Simon Knott 提交于
Closes #12045 This PR adds support for [etags](https://tools.ietf.org/html/rfc7232#section-3.2) to Next.js' API routes, which will improve user experience and decrease network traffic by enabling usage of etag-based caching.
-
由 Todor Totev 提交于
* Moved the state to the clock component * Refactored the store according to the new requirements * Refactored _app so it uses the new store * This file is no longer needed Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Thor 雷神 提交于
- Update to latest stripe-node version and pin the exact version so the Types won't go out of sync - Add the env var changes for next 9.4.4 (https://nextjs.org/blog/next-9-4#new-environment-variables-support) - Remove `next.config.js` as no longer needed. - Add the Deploy to Vercel button
-
由 MichelleLucero 提交于
* created with-mongodb, Next.js + MongoDB Co-authored-by: NShania Dhani <31454777+sdhani@users.noreply.github.com> Co-authored-by: NMichelle Lucero <31500626+MichelleLucero@users.noreply.github.com> Co-authored-by: NChi Shing Lee <60354073+chislee0708@users.noreply.github.com> * Update examples/with-mongodb/README.md Co-authored-by: NTim Neutkens <tim@timneutkens.nl> * modified for dotenv and environment var setup * removed extra instructions on readme, linked it to the MongoDB guides * changes to environment var * replaced document with react logic * removed Pet header * removed isomorphic-unfetch * replaced getInitialProps with getStaticProps (SSG) * removed console log * deleted next.config.js file * fixed prettier styling * fixed link 404 server rendering issue * modified server path for delete/edit * fixed prettier styling * fixed a typo * change .env to .env.local Co-authored-by: NJoe Haddad <timer150@gmail.com> * fixed typo, change .env to .env.local Co-authored-by: NJoe Haddad <timer150@gmail.com> * change .env to .env.local Co-authored-by: NJoe Haddad <timer150@gmail.com> * Update examples/with-mongodb/package.json Co-authored-by: NJoe Haddad <timer150@gmail.com> * removed dotenv dev dependency Co-authored-by: NJoe Haddad <timer150@gmail.com> * cleaned up code and instructions * Update examples/with-mongodb/.gitignore Co-authored-by: NLuis Alvarez D. <luis@vercel.com> * minor changes to code style and logic * Updated index page and .env.local.example * Updated new page * Don't use SSG for the edit page * Fixed revalidation issue * Use es6 for the model * Updated edit page * Removed VERCEL_URL * Updated readme and renamed env * Added temporal vercel.json * Removed seed until added with a script * Updated package.json * Renamed example in readme * Renamed example * Lint fix Co-authored-by: Nliulanz <zhengliulan@gmail.com> Co-authored-by: NShania Dhani <31454777+sdhani@users.noreply.github.com> Co-authored-by: NChi Shing Lee <60354073+chislee0708@users.noreply.github.com> Co-authored-by: NTim Neutkens <tim@timneutkens.nl> Co-authored-by: Nsdhani <shania.dhani46@myhunter.cuny.edu> Co-authored-by: Nliulanz <37808313+liulanz@users.noreply.github.com> Co-authored-by: NJoe Haddad <timer150@gmail.com> Co-authored-by: NLuis Alvarez D. <luis@vercel.com>
-
- 30 5月, 2020 3 次提交
-
-
由 Martin Bavio 提交于
This PR fixes https://github.com/vercel/next.js/issues/7769. However, I would like for @jayu to confirm that it's ok to use the latest Linaria 2.0 alpha release. I can confirm from my local testing that it's working as expected.
-
由 Pavel Korotenko 提交于
Updates docs for AMP validation with usage examples for custom validators added in #9191 and `skipValidation` mode added in #10705
-
由 JJ Kasper 提交于
Since non-fallback pages don't rely on the URL for hydration we can allow them to be rewritten to but pages with fallback still can't be rewritten to because we won't be able to parse the correct `/_next/data` path to request the page's data from. I added a test for this behavior and ensured it works correctly on Now. Example on with fallback false rewrite on Now: https://tst-rewrite-cp9vge4bg.now.sh/about
-
- 29 5月, 2020 16 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
This code existed mostly to work around webpack 2 (yes 2.x) limitations where it crashed in certain cases where files didn't exist anymore. We have tests for that behavior and latest webpack has fixed these. Hence why this can be removed
👍 -
由 Tim Neutkens 提交于
Updates the message to be in line with .env loading.
-
由 Kristoffer K 提交于
-
由 Tim Neutkens 提交于
-
由 Joe Haddad 提交于
This removes `fork-ts-checker-webpack-plugin` and instead directly calls the TypeScript API. This is approximately 10x faster. Base build: 7s (no TypeScript features enabled) - `fork-ts-checker-webpack-plugin@3.1.1`: 90s, computer sounds like an airplane - `fork-ts-checker-webpack-plugin@4.1.6`: 84s, computer did **not** sound like an airplane - `fork-ts-checker-webpack-plugin@5.0.0-alpha.14`: 90s, regressed - `npx tsc -p tsconfig.json --noEmit`: 12s (time: `18.57s user 0.97s system 169% cpu 11.525 total`) - **This PR**: 22s, expected to get better when we run this as a side-car All of these tests were run 3 times and repeat-accurate within +/- 0.5s.
-
由 Joe Haddad 提交于
This PR checks if our tests can be ran faster by disabling source maps unless they're used for the purpose of testing.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
This pull request refactors our TypeScript preflight check in preparation for dropping the `fork-ts-checker-webpack-plugin` plugin. This will make reviewing the subsequent PR much easier. --- There is no behavior change, so the existing test should cover this adequately.
-
由 Jan Potoms 提交于
Running ``` yarn ``` in the project while on node.js 14 results into errors with the `grpc` dependency of `firebase`. Updating `firebase` fixes that.
-
由 Michael Albertz 提交于
Resolves: https://github.com/zeit/next.js/issues/12545 This PR adds an example which show how to bundle and use WebWorkers in a next.js app. The issue mentions Typescript, but adding typescript to the example should be fairly simple by following the documentation and seems out of scope for a web-worker example.
-
由 Joe Haddad 提交于
By default, webpack will proceed to run loaders and plugins on all files, even after an error has been encountered during the build process. This means you might need to wait minutes to see a syntax error encountered in one of your source files. This PR fixes that.
-
由 Aral Roca Gomez 提交于
Fix a typo.
-
由 Prateek Bhatnagar 提交于
-
由 Rubén Sospedra 提交于
Motivated by the need to deploy static sites while having a good i18n support¹ ² @vinissimus developed [next-translate](https://github.com/vinissimus/next-translate). Here's the example ;) References: 1. https://github.com/vercel/next.js/discussions/10651 2. https://github.com/vercel/next.js/pull/12535#issuecomment-624317275
-
由 Mathis Chenuet 提交于
The current example doesn't work if one try to reproduce it with a recent version of http-proxy-middleware.
-
- 28 5月, 2020 17 次提交
-
-
由 Tim Neutkens 提交于
-
由 Joe Haddad 提交于
Co-authored-by: Nkodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
-
由 Joe Haddad 提交于
After #12361, I've seen a few users ask "but why". This PR updates the err.sh link to better explain the restriction. It also provides an alternative!
-
由 Joe Haddad 提交于
This adds a lint rule to ensure we don't import dev dependencies by accident.
-
由 Chandu 提交于
@lfades hope this works. I have updated the example to show differences between client/ssr/ssg initial state in redux. Let me know if something needs to be changed.
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
As reported here: https://twitter.com/vvoyer/status/1246913957899763712?s=21
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Joe Haddad 提交于
-
由 Jimmy Merritello 提交于
### Add dynamic routes to _with-route-as-modal_ example This PR adds [dynamic routes](https://nextjs.org/docs/routing/dynamic-routes), [getStaticPaths](https://nextjs.org/docs/basic-features/data-fetching#getstaticpaths-static-generation), and [getStaticProps](https://nextjs.org/docs/basic-features/data-fetching#getstaticprops-static-generation) to the **with-route-as-modal** example. This change might also clear up some confusion here on https://github.com/zeit/next.js/issues/11971 Additionally this PR makes sure each modal route is also a modal **page.** This is an important distinction and makes sure the experience is the same should the URL (route) be shared as a link. In other words, `index.js` need not be the only "entrypoint" to browsing the website. With the additions in this PR, each post page is an actual page, so if you were to share the link for **Post 3** you'd get this: <img src="https://user-images.githubusercontent.com/7191639/82058282-25ad7780-968a-11ea-94f1-9b4a36abccf9.png" width="200px" /> (clickable outer region brings you back to the 'gallery') **Update:** I have also included the `pathname` to signal the difference in which page component is rendered Rather than this (previously): <img src="https://user-images.githubusercontent.com/7191639/82058199-0878a900-968a-11ea-97d2-e9e20c9267fc.png" width="200px" /> I have used a similar approach [here
🔗 ](https://hashiconf.com/digital-june/schedule/the-hitchhikers-guide-to-terraform-your-infrastructure) -
由 Karl Horky 提交于
Netlify Plugins are out of beta! https://www.netlify.com/blog/2020/05/27/netlify-build-plugins-are-here/
-
由 Manu Schiller 提交于
This adds `InferredStaticProps` and `InferredServerSideProps` to the typings. - [x] add types for type inference - [x] add explanation to docs - [ ] tests - are there any? ![inferred-props](https://user-images.githubusercontent.com/56154253/79068041-24bcab00-7cc4-11ea-8397-ed1b95fbeca7.gif) ### What does it do: As an alternative to declaring your Types manually with: ```typescript type Props = { posts: Post[] } export const getStaticProps: GetStaticProps<Props> = () => ({ posts: await fetchMyPosts(), }) export const MyComponent(props: Props) =>( // ... ); ``` we can now also infer the prop types with ```typescript export const getStaticProps = () => ({ // given fetchMyPosts() returns type Post[] posts: await fetchMyPosts(), }) export const MyComponent(props: InferredStaticProps<typeof getStaticProps>) =>( // props.posts will be of type Post[] ); ``` ### help / review wanted - [ ] I am no typescript expert. Although the solution works as intended for me, someone with more knowledge could probably improve the types. Any edge cases I missed? - [ ] are there any tests I should modify/ add?
-
由 Joe Haddad 提交于
This pull request updates our TypeScript verification process to not wipe out potentially vital user comments. Introducing a prompt process was mostly a side effect of users wanting to keep comments. There's no reason we really need this prompt, as answering no would refuse to boot the Next.js server anyway. --- Fixes #8128 Closes #11440
-
由 Stephen Cefali 提交于
Co-authored-by: NJoe Haddad <joe.haddad@zeit.co>
-