- 20 10月, 2017 2 次提交
-
-
由 Kevin Decker 提交于
* Propagate source maps through combine assets step * Use constant development build id
-
由 Dylan Staley 提交于
-
- 19 10月, 2017 1 次提交
-
-
由 Li Weinan 提交于
* update dependnecies * keep next version as `latest` and depend on `react@^16.0.0`
-
- 18 10月, 2017 2 次提交
-
-
由 Kevin Decker 提交于
-
* jest example updated * reverted changes on yarn.lock
-
- 17 10月, 2017 4 次提交
-
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
-
由 Olivier Tassinari 提交于
-
由 Stephen Daves 提交于
-
- 16 10月, 2017 7 次提交
-
-
由 Tim Neutkens 提交于
* Upgrade dependency on next * Add styled-jsx-plugin-sass example * Update readme
-
由 Connor Bär 提交于
-
由 Arunoda Susiripala 提交于
-
由 Tim Neutkens 提交于
-
由 Kevin Decker 提交于
This drops a few kb off of the production min+gz build due to the remove of the component and a ew dependencies that it references, ansi-html being the biggest.
-
由 Tim Neutkens 提交于
-
由 Tim Neutkens 提交于
* Make styled-jsx configurable * Add styled-jsx-plugin-postcss example * Add styled-jsx 2.1.0 with plugins support * Move examples around and add description * Add link to new example
-
- 15 10月, 2017 5 次提交
-
-
由 yashha 提交于
-
由 Tim Neutkens 提交于
-
由 Tomas Roos 提交于
Running nsp check ``` ➜ web git:(master) nsp check (+) 1 vulnerabilities found ┌───────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ │ Regular Expression Denial of Service │ ├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Name │ mime │ ├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ CVSS │ 7.5 (High) │ ├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Installed │ 1.3.4 │ ├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Vulnerable │ < 1.4.1 || > 2.0.0 < 2.0.3 │ ├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Patched │ >= 1.4.1 < 2.0.0 || >= 2.0.3 │ ├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ Path │ web@1.0.0 > next@4.0.1 > send@0.15.6 > mime@1.3.4 │ ├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────┤ │ More Info │ https://nodesecurity.io/advisories/535 │ └───────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ ``` This is a dependency of send which already upgraded this in order to not be exposed to this known error. https://github.com/pillarjs/send/blob/master/HISTORY.md
-
由 Kevin Decker 提交于
The next object was not being exported in the same manner in dev vs. prod mode.
-
由 Sitian Liu 提交于
-
- 14 10月, 2017 2 次提交
-
-
* Update babel-preset.js As './dist/server/build/babel/preset' now return a function, in this example we need to first call the function and after that replace styled-jsx * linting issues solved
-
由 Sitian Liu 提交于
Firebase server side auth example update: don't fetch messages server-side if user is not found (#3087) * don't fetch messages server-side if user is not found Currently, the component always fetch everything under '/messages' even if the user is not authenticated on the server side. Update it to not fetch if the user is not found as a better example on handling. * fix lint error
-
- 12 10月, 2017 2 次提交
-
-
由 Kohei Hasegawa 提交于
-
由 Eric Redon 提交于
* Fix with-global-stylesheet example by depending on React≥16 * Bump other dependencies of with-global-stylesheet example
-
- 11 10月, 2017 4 次提交
-
-
由 Arunoda Susiripala 提交于
-
由 Zach Brown 提交于
-
由 Tim Neutkens 提交于
-
由 Giuseppe 提交于
-
- 10 10月, 2017 8 次提交
-
-
由 Matheus Fernandes 提交于
-
由 Hugo Meissner 提交于
* emotion v8 + adjustments for breaking changes * Corrected versioning * Take hydrate from 'react-emotion' I was actually wondering that, but haven't seen hydrate in the medium post (even though you pointed out that react-emotion exports all of emotion and I've seen it in source) and didn't want to risk it for the off chance that it *should* be imported directly from emotion for some reason :D
-
由 Simon Hänisch 提交于
There was a missing "is" in one of the sentences.
-
由 Arunoda Susiripala 提交于
-
由 Arunoda Susiripala 提交于
This usually helps when upgrading Next.js.
-
由 Arunoda Susiripala 提交于
-
由 Arunoda Susiripala 提交于
-
由 Arunoda Susiripala 提交于
-
- 08 10月, 2017 3 次提交
-
-
由 Guilherme Diego 提交于
-
由 Arunoda Susiripala 提交于
-
由 Giuseppe 提交于
-