1. 03 Mar, 2019 2 commits
  2. 02 Mar, 2019 4 commits
  3. 01 Mar, 2019 9 commits
  4. 28 Feb, 2019 9 commits
  5. 27 Feb, 2019 10 commits
    • JJ Kasper's avatar
      Add styles to experimental-amp example (#6461) · 23178db5
      JJ Kasper authored
      After discussion added global styles to experimental-amp example
      23178db5
    • JJ Kasper's avatar
    • Joe Haddad's avatar
      Change ncc taskr function name (#6471) · 227ea575
      Joe Haddad authored
      227ea575
    • Joe Haddad's avatar
      Run ncc on unistore to fix install warning (#6459) · 41eaa9cf
      Joe Haddad authored
      ncc unistore to fix install warning
      41eaa9cf
    • Tim Neutkens's avatar
      v8.0.4-canary.4 · 88388f79
      Tim Neutkens authored
      88388f79
    • Kiko Beats's avatar
      Use cacheable-response for ssr (#6393) · 3998805b
      Kiko Beats authored
      Hello,
      
      I have been using next.js for a while in a bunch of projects, so first for all thanks for all the vibrant effort around the project 🖤. 
      
      Always I see the server side next.js approach as an advantage, but also a weakness for the extra resources you need to have, specially comparing how cheap is a client side app.
      
      In order to do my things cheaper, I started using the SSR pattern you suggested in your examples, so useful! It saves time and resources.
      
      However, it was *too simple*. In a real production scenario, you need a bit more, specially related with send the right response headers to keep the rest of external network agent updated of your cache state.
      
      I started a tiny script code for doing that; basically, I copy/paste it on my ssr projects.
      
      Now, after a time, I think it's worth it publish it as [cacheable-response](https://github.com/Kikobeats/cacheable-response) module.
      
      The PR is for adding the module leverage into the next.js ssr example. 
      
      It's doing the same, plus:
      
      - be possible use a multi storage cache (memory by default; mongodb, redis, mysql, supported).
      - sending `cache-control` response headers.
      - sending `X-Cache-Expired-At`, just a humanize way to see the expiration time.
      - support for forcing invalidation via `force=true` query parameter.
      
      I hope you like it 🙂
      3998805b
    • Samundra Shrestha's avatar
      add extra info to authentication (#6435) · aed7f643
      Samundra Shrestha authored
      * add extra info to authentication
      
      * Update auth.js
      aed7f643
    • Luc's avatar
      Update with-jest, with-jest-react-testing-library examples (#6464) · 806bfdfa
      Luc authored
      The latest version of babel-jest doesn't require `babel-core` with the bridge version anymore (updated in this PR : https://github.com/facebook/jest/pull/7016).
      
      So I'm updating with-jest and with-jest-react-testing-library examples accordingly.
      806bfdfa
    • Peter Kellner's avatar
      Create example for adding env variables from next.js.config / Final (#6318) · 62f84bb1
      Peter Kellner authored
      * This is a non-working example of using PHASE_DEVELOPMENT_SERVER and PHASE_PRODUCTION_SERVER in production. I followed @timneutkens gist but was unable to make it work so I've boiled it down into this non-working example which I believe is the same.  The README is not updated. Once it is figured out why this is not working, I'll clean up the project and update the pull request to be complete but for now just want to make it work.
      
      * added .eslintrc so that ` eslint . --fix` would work (not sure if that was really necessary). I assume that is same as `yarn lint-fix`.
      
      * fixes for standard style
      
      * fixes for standard style
      
      * Fix example and add some comments
      
      * Updated documentation and small change to logic of prod,dev,staging to work as expected.
      Added significantly more doc then I normally would in the hopes that it helps someone avoid the mis-understanding I went through.  If it's too much, LMK and I'll reduce.
      
      * removed eslint and updated package.json to get rid of eslint and standardjs
      62f84bb1
    • JJ Kasper's avatar
      Remove next-to-next-server babel plugin (#6458) · 256970ac
      JJ Kasper authored
      After discussion it was decided instead of rewriting `next/config` and `next/head` imports to `next-server/config` and `next-server/head` we should just allow importing them as `next/config` and `next/head`
       
      Fixes: #6187
      256970ac
  6. 26 Feb, 2019 6 commits