{"push_id":2849606669,"size":121,"distinct_size":121,"ref":"refs/heads/canary","head":"56937fd22c4ff6d2dc03dfec09332f9ac057d380","before":"183866a96db9a6bcf23c653ecc42de017d1cb519","commits":[{"sha":"b65d2dff303ba1f4d240491ef72e94826c82d7d9","author":{"name":"Tim Neutkens","email":"c2906527566e870efadc59ea5d0cd9114389a5d9@me.com"},"message":"6.1.1-canary.3","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/b65d2dff303ba1f4d240491ef72e94826c82d7d9"},{"sha":"9240cf7855dfc3c760df89daf1fbadeedfa9606f","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Make `.events` work even when router is not initialized (#4874)\n\nFollowup of https://github.com/zeit/next.js/issues/4863#issuecomment-408920755","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/9240cf7855dfc3c760df89daf1fbadeedfa9606f"},{"sha":"59c7d42d36b4fbf2ab5e5303a2e7153dfb55a9c8","author":{"name":"Tim Neutkens","email":"c2906527566e870efadc59ea5d0cd9114389a5d9@me.com"},"message":"6.1.1-canary.4","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/59c7d42d36b4fbf2ab5e5303a2e7153dfb55a9c8"},{"sha":"80202069cfd5161db4511fb4fd2e09f9c664ff5f","author":{"name":"Max Stoiber","email":"1a73af9e7ae00182733b2292511b814be66f065f@mxstbr.com"},"message":"Note babel-plugin-styled-components (#4882)\n\nOtherwise folks might miss that part and get checksum mismatches!","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/80202069cfd5161db4511fb4fd2e09f9c664ff5f"},{"sha":"b492e6703de62e1b4a63957350108ce8db6eeb68","author":{"name":"Jacob Page","email":"66cb798984d2d0e782cb1a7c23ff47819606b5fb@godaddy.com"},"message":"Make EventEmitter more Node-like (#4865)\n\nAdd behaviors to make `EventEmitter` a bit more like its NodeJS counterpart. This should make using it a bit less surprising.","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/b492e6703de62e1b4a63957350108ce8db6eeb68"},{"sha":"bd3f65b37f917e212e8fa194df3cc4b1e923b20b","author":{"name":"Sayuti Daniel","email":"919c026dacec243621ef1a019379583d18ea2632@traveloka.com"},"message":"Use contenthash instead of chunkhash (#4894)\n\nhttps://github.com/webpack/webpack.js.org/issues/2096","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/bd3f65b37f917e212e8fa194df3cc4b1e923b20b"},{"sha":"b1459bfd60d23dfb73e0425badf4f693046077ad","author":{"name":"Tomek","email":"13d495931307f18f8a98534fbc59821d71850a21@gmail.com"},"message":"update with-sentry example (#4859)\n\nChanges:\r\n\r\n* moved the configuration from HOC to `_app.js`\r\n* fixed the example, as `componentDidCatch` catches errors during rendering phase, but not within event handlers.","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/b1459bfd60d23dfb73e0425badf4f693046077ad"},{"sha":"919b88509ceb48af46f2c8b2ac343ec3b0c380e4","author":{"name":"Sayuti Daniel","email":"919c026dacec243621ef1a019379583d18ea2632@traveloka.com"},"message":"Let webpack handle contenthash (#4895)","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/919b88509ceb48af46f2c8b2ac343ec3b0c380e4"},{"sha":"05b68916202041e56ed29ca492070c764dcca235","author":{"name":"Kate","email":"88954c3b1e35e6ca6b8aba68ee9dceee8d6d9903@ya.ru"},"message":"Fixed server status message in with-redux-observable-example. (#4900)\n\n**Changes:**\r\n- Fixed \"was character fetched on server\" message by properly passing `isServer`.\r\n- Stop fetching if there was an error (currently it keeps sending requests to the same endpoint every 3 sec)\r\n\r\n**Related:**\r\n- https://github.com/zeit/next.js/pull/4818\r\n- https://github.com/zeit/next.js/issues/4724","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/05b68916202041e56ed29ca492070c764dcca235"},{"sha":"a41e3c102e509db93f62be34eb782f73e43f95a7","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Await preloading right before rendering the page (#4896)","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/a41e3c102e509db93f62be34eb782f73e43f95a7"},{"sha":"e8aa78204aafe4b1cb97226d670b4474d536a683","author":{"name":"Hugo Heyman","email":"1241636c38d6ab028d78164d8e5518b151d9d918@gmail.com"},"message":"Improve glamor example (#4893)\n\nChanges:\r\n- Use css prop on the element to style it\r\n- Add webpack + babelrc configuration to remove otherwise needed import boilerplate [according to glamor docs](https://github.com/threepointone/glamor/blob/master/docs/createElement.md)\r\n\r\nRationale: The killer feature of glamor that makes it so great is that it relieves you from naming classes/styles if you use the custom css prop. Together with the babel plugin you also don't need any extra import wherever the css prop is used.\r\n\r\nAll the real world uses I've seen of glamor has used the css props so I think the example should reflect this. As an example here is docs how to use glamor with gatsby (using the css prop):\r\nhttps://www.gatsbyjs.org/docs/glamor/","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/e8aa78204aafe4b1cb97226d670b4474d536a683"},{"sha":"83970c908d808a48175382f2df62bac579b0df26","author":{"name":"Thomas Hermann","email":"e9e5f785a7f3fcc20ab90dd8ccb760a28617cd9e@gmail.com"},"message":"Add with-strict-csp example (#4858)","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/83970c908d808a48175382f2df62bac579b0df26"},{"sha":"4c602ff39559bc0d04c0e0136e87e9caf9d75295","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Run manual-bind-to-arrow codemod (#4906)\n\nhttps://github.com/reactjs/react-codemod#manual-bind-to-arrow","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/4c602ff39559bc0d04c0e0136e87e9caf9d75295"},{"sha":"b20b80adf099db669c55936fe092a8d4bd9d7d39","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Run rename-unsafe-lifecycles as preparation for React 17 (#4907)\n\nhttps://github.com/reactjs/react-codemod#rename-unsafe-lifecycles","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/b20b80adf099db669c55936fe092a8d4bd9d7d39"},{"sha":"80fdfec088408249594b8c2f1bf24ab59e974595","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Fix decorator warnings (#4910)","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/80fdfec088408249594b8c2f1bf24ab59e974595"},{"sha":"f3f939dde4c06eb7be88dfac671d015d3724e2be","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Run method sorting codemod (#4909)\n\nreact-codemod recommended way of having methods defined","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/f3f939dde4c06eb7be88dfac671d015d3724e2be"},{"sha":"3286ecb3fca0f7df2ef88a00b6e51c041dc4f95c","author":{"name":"HaNdTriX","email":"b030d5fbdcf6975bff778d3027f2c1d5802fe031@users.noreply.github.com"},"message":"Add slate.js example (#4899)","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/3286ecb3fca0f7df2ef88a00b6e51c041dc4f95c"},{"sha":"a528565c6918793472bb4c09a351e561f98ba27d","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Make next/link async safe (#4911)\n\nRemoves componentWillMount and uses memoize instead as recommended here: https://reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/a528565c6918793472bb4c09a351e561f98ba27d"},{"sha":"6de99ebc4a2cbfbb4d6b6481239dfece7848047e","author":{"name":"Tim Neutkens","email":"5ee0edb9e2229c0838f1959779f1949031de0123@timneutkens.nl"},"message":"Set correct status for sigint (#4917)\n\nFixes #4916","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/6de99ebc4a2cbfbb4d6b6481239dfece7848047e"},{"sha":"b50bad56bee89ab006b643483c641af28aeefae2","author":{"name":"Connor Bär","email":"d1c170759c0cbb454f32756a64191b8b2b7be5ab@users.noreply.github.com"},"message":"[BUG] Fix emit-file-loader compatibility with Webpack 4 (#4918)\n\n## Context\r\n\r\nWhen upgrading to Next.js 6.1.1-canary.4 and using the `emit-file-loader` included in Next.js, the following error is thrown:\r\n\r\n```bash\r\n error  in ./src/graveyard/pages/_app.scss\r\nModule build failed (from ../node_modules/next/dist/build/webpack/loaders/emit-file-loader.js):\r\nTypeError: Cannot read property 'context' of undefined\r\n    at Object.module.exports (~/project-root/node_modules/next/dist/build/webpack/load\r\ners/emit-file-loader.js:27:68)\r\n\r\n @ ./src/pages/_app.js 35:0-53 156:17-26 157:13-22\r\n @ multi ./pages/_app.js\r\n```\r\n\r\n`next.config.js` (shortened):\r\n```js\r\nmodule.exports = {\r\n  webpack: (config, { dev }) => {\r\n    config.module.rules.push({\r\n      test: /\\.scss$/,\r\n      use: [\r\n        {\r\n          loader: 'emit-file-loader',\r\n          options: {\r\n            name: 'dist/[path][name].[ext].js'\r\n          }\r\n        },\r\n        {\r\n          loader: 'babel-loader',\r\n          options: {\r\n            babelrc: false,\r\n            extends: path.resolve(__dirname, './src/.babelrc')\r\n          }\r\n        },\r\n        'styled-jsx-css-loader',\r\n        { loader: 'postcss-loader', options: { sourceMap: dev } },\r\n        {\r\n          loader: 'sass-loader',\r\n          options: {\r\n            sourceMap: dev\r\n          }\r\n        }\r\n      ]\r\n    });\r\n\r\n    return config;\r\n  }\r\n};\r\n```\r\n\r\n## Suggested Fix\r\n\r\nA quick Google search brought me to a [related issue in `webpack-loader`](https://github.com/webpack-contrib/worker-loader/issues/125). As pointed out in the [Webpack docs](https://webpack.js.org/api/loaders/#this-rootcontext):\r\n\r\n> Starting with webpack 4, the formerly `this.options.context` is provided as `this.rootContext`.\r\n\r\nThis PR makes this change while maintaining backward compatibility.\r\n\r\n## System information\r\n\r\nNext.js: 6.1.1-canary.4\r\nNode: v9.3.0","distinct":true,"url":"https://api.github.com/repos/DullReferenceException/next.js/commits/b50bad56bee89ab006b643483c641af28aeefae2"}]}
{"actor":{"display_login":"DullReferenceException"}}