1. 19 3月, 2019 1 次提交
  2. 14 3月, 2019 2 次提交
  3. 12 3月, 2019 1 次提交
  4. 20 2月, 2019 1 次提交
  5. 14 2月, 2019 1 次提交
    • T
      [experimental] Rendering to AMP (#6218) · 4051ffcb
      Tim Neutkens 提交于
      * Add initial AMP implementation
      
      * Implement experimental feature flag
      
      * Implement feedback from sbenz
      
      * Add next/amp and `useAmp` hook
      
      * Use /:path*/amp instead
      
      * Add canonical
      
      * Add amphtml tag
      
      * Add ampEnabled for rel=“amphtml”
      
      * Remove extra type
      4051ffcb
  6. 03 2月, 2019 1 次提交
  7. 26 1月, 2019 1 次提交
  8. 23 1月, 2019 1 次提交
  9. 19 12月, 2018 1 次提交
    • T
      Move out requires from renderToHTML (#5915) · 32451e97
      Tim Neutkens 提交于
      This brings us one step closer to outputting serverless functions as renderToHTML now renders the passed components, which allows us to bundle the renderToHTML function together with statically imported components in webpack.
      32451e97
  10. 17 12月, 2018 1 次提交
    • B
      Improve dev experience by listening faster (#5902) · b91a9601
      Brian Beck 提交于
      As I detailed in [this thread on Spectrum](https://spectrum.chat/?t=3df7b1fb-7331-4ca4-af35-d9a8b1cacb2c), the dev experience would be a lot nicer if the server started listening as soon as possible, before the slow initialization steps. That way, instead of manually polling the dev URL until the server's up (this can take a long time!), I can open it right away and the responses will be delivered when the dev server is done initializing.
      
      This makes a few changes to the dev server:
      
      * Move `HotReloader` creation to `prepare`. Ideally, more things (from the non-dev `Server`) would be moved to a later point as well, because creating `next({ ... })` is quite slow.
      * In `run`, wait for a promise to resolve before doing anything. This promise automatically gets resolved whenever `prepare` finishes successfully.
      
      And the `next dev` and `next start` scripts:
      
      * Since we want to log that the server is ready/listening before the intensive build process kicks off, we return the app instance from `startServer` and the scripts call `app.prepare()`.
      
      This should all be backwards compatible, including with all existing custom server recommendations that essentially say `app.prepare().then(listen)`. But now, we could make an even better recommendation: start listening right away, then call `app.prepare()` in the `listen` callback. Users would be free to make that change and get better DX.
      
      Try it and I doubt you'll want to go back to the old way. :)
      b91a9601
  11. 10 12月, 2018 1 次提交
  12. 03 11月, 2018 1 次提交
  13. 03 10月, 2018 1 次提交
  14. 02 10月, 2018 1 次提交
  15. 01 10月, 2018 2 次提交
  16. 29 9月, 2018 1 次提交
  17. 28 9月, 2018 2 次提交