Next.js: 2.0 checklist

[rauchg]

• [x] next.config.js
• [x] Upgrade to Webpack 2.0 #287
• [x] Switch to more optimized main bundle / ditch CDN
• [x] Document singleton Router API
• [x] Document programmatic server API in README
• [x] Add config.babel Object + Function support
  
  
  
  • [x] Document adding an additional babel transformation in README (do-expressions)
  
  
• [x] Make sure we flush head and CSS upon errors #439
• [x] Add missing READMEs in examples/ and link to them throughout the README
• [x] Document usage of SSR styling solutions with <Document> in examples/
  
  
  
  • [x] glamor
  
  
  • [x] styled-components
  
  
  • [x] styletron
  
  
• [x] Incorporate styled-jsx and update
  
  
  
  • [x] Readme
  
  
  • [ ] Blog post
  
  
  • [x] Examples
  
  
• [x] Show dev-mode deprecation for pushTo and replaceTo
• [x] Show dev-mode deprecation notice for next/css and point to the glamor example
• [ ] Router events

[lukeed]

IMO, for a 2.0 release, glamor should be removed entirely (as a breaking change) instead of showing a dev-only deprecation message. This still includes it within the bundle.

This route would have made sense if 1.3 was the next target release.

Happy to tackle this if it's wanted.

[rauchg]

@lukeed I want to give people some time to migrate away. We can do a 3.0 release soon that removes it.

Right now I'm working on the guide that explains how to set up <Document> and include glamor in dependencies and then just use import 'glamor'

Also, to alleviate any bloat concerns: if the module is not imported, it's not included in the builds. That's true of both next/css and <style jsx>.

[frol]

3.0 release is coming, so this issue can be closed, I suppose :)

[arunoda]

Yes it is :)