rsnext/examples/with-glamor/package.json

{
  "name": "with-glamor",
  "version": "1.0.0",
  "scripts": {
    "dev": "next",
    "build": "next build",
    "start": "next start"
  },
  "dependencies": {
    "glamor": "^2.20.24",
    "next": "^2.0.0-beta",
    "react": "^15.4.2",
    "react-dom": "^15.4.2"
  },
  "author": "",
  "license": "ISC"
}
Added glamor example and pointing warning to css migration guide (#500) 2016-12-23 20:18:25 +01:00			`{`
			`"name": "with-glamor",`
			`"version": "1.0.0",`
			`"scripts": {`
			`"dev": "next",`
			`"build": "next build",`
			`"start": "next start"`
			`},`
			`"dependencies": {`
Remove traces of glamor (#1286) * Remove traces of glamor As talked about with @rauchg. Glamor takes up around 60KB of the bundle (pre-gzip). Since styled-jsx is the way to go now and we support adding glamor by the user we should remove it as dependency cause it is bundled even when not used. Added rehydration to the example, since we did that in our code. There is only one thing I'm not sure about and want to discuss: what should we do with next/css. Right now I added a throw for when it is imported. I'm not sure if we should do that / some other way to notify the user it has been removed. The reasoning behind the throw is that when we would do a console.warn the user would see 'css.default.<X>' not found because we don't have the glamor dependency anymore. * Update yarn.lock * Remove test for styles 2017-02-26 13:28:00 +01:00			`"glamor": "^2.20.24",`
add react and react dom as peer (#1024) - tackles #997 - add ./idea to gitignore for webstorm users - update all the examples 2017-02-08 05:41:38 +01:00			`"next": "^2.0.0-beta",`
			`"react": "^15.4.2",`
			`"react-dom": "^15.4.2"`
Added glamor example and pointing warning to css migration guide (#500) 2016-12-23 20:18:25 +01:00			`},`
			`"author": "",`
			`"license": "ISC"`
			`}`