- 17 12月, 2016 6 次提交
-
-
由 nkzawa 提交于
-
由 Naoyuki Kanezawa 提交于
* add 'next' api * add render APIs * add 'as' prop to Link * check Accept header to serve json response * check if response was finished on getInitialProps call * move server/app to server/index * load webpack-hot-middleware-client by absolute path * server: options for testing * add tests * example: improve * server: make dir optional * fix client routing * add parameterized routing example * link: fix display url * Add custom-server-express example (#352) * Add custom-server-express example * Remove extraneous nexts in express routes defs * Update next config in server.js * Handle accept headers totally inside Next.js (#385) * Handle accept headers totally inside Next.js Now user doesn't need to handle it anymore. * Move json pages serving to /_next/pages base path. * Join paths correctly. * remove next/render
-
由 Guillermo Rauch 提交于
-
由 Guillermo Rauch 提交于
-
由 nkzawa 提交于
-
由 Naoyuki Kanezawa 提交于
-
- 16 12月, 2016 5 次提交
-
-
由 Arunoda Susiripala 提交于
-
由 Arunoda Susiripala 提交于
React addons require React in a special way. That causes Webpack to push React into the app's bundle. This fix adds new externals entries to prevent that.
-
由 Dmitry Poddubniy 提交于
* fixed bug #362, also set chunks names * set simple solution for minChunks * revert in favor of #310
-
由 Matthew Mueller 提交于
-
由 Arunoda Susiripala 提交于
* Register the service worker. * Update prefetcher code to do prefetching. * Implement the core prefetching API. support "import <Link>, { prefetch } from 'next/prefetch'" * Implement a better communication system with the service worker. * Add a separate example for prefetching * Fix some typos. * Initiate service worker support even prefetching is not used. This is pretty important since initiating will reset the cache. If we don't do this, it's possible to have old cached resources after the user decided to remove all of the prefetching logic. In this case, even the page didn't prefetch it'll use the previously cached pages. That because of there might be a already running service worker. * Use url module to get pathname. * Move prefetcher code to the client from pages Now we also do a webpack build for the prefetcher code. * Add prefetching docs to the README.md * Fix some typo. * Register service worker only if asked to prefetch We also clean the cache always, even we initialize the service worker or not.
-
- 15 12月, 2016 2 次提交
-
-
由 Matthew Mueller 提交于
-
由 Matthew Mueller 提交于
-
- 13 12月, 2016 1 次提交
-
-
由 Chris 提交于
- was using `]` instead of `}`
-
- 12 12月, 2016 2 次提交
-
-
由 Benjamin E. Coe 提交于
-
由 Stephen Sauceda 提交于
* use next logo on 'init' start page * use github cdn for logo
-
- 11 12月, 2016 1 次提交
-
-
由 nkzawa 提交于
-
- 09 12月, 2016 7 次提交
-
-
由 Greenkeeper 提交于
-
由 Greenkeeper 提交于
-
由 Greenkeeper 提交于
-
由 Greenkeeper 提交于
-
由 Greenkeeper 提交于
-
由 Greenkeeper 提交于
-
由 Guillermo Rauch 提交于
-
- 07 12月, 2016 4 次提交
-
-
由 Luke Edwards 提交于
-
-
由 Leo Lamprecht 提交于
-
由 Leo Lamprecht 提交于
Now outputs a URL by itself
-
- 06 12月, 2016 5 次提交
-
-
由 Arunoda Susiripala 提交于
Earlier it was for all length of entry points. But we add two more entry points for errors. Because of that, moving common modules to commons.js won't work.
-
由 Naoyuki Kanezawa 提交于
-
由 Naoyuki Kanezawa 提交于
-
由 Greenkeeper 提交于
-
由 Chua Kiem Fai 提交于
Fix following issue in Docker https://github.com/IanMitchell/is-windows-bash/pull/2 https://github.com/zeit/next.js/issues/344
-
- 04 12月, 2016 3 次提交
-
-
由 nkzawa 提交于
-
由 nkzawa 提交于
-
由 Greenkeeper 提交于
-
- 03 12月, 2016 1 次提交
-
-
由 Matheus Fernandes 提交于
-
- 02 12月, 2016 3 次提交
-
-
由 Greenkeeper 提交于
-
由 Sébastien Dubois 提交于
-
由 nkzawa 提交于
-