Tim Neutkens 2a50c176cf Make HMR still apply updates when there is a webpack warning (#6099) ... Fixes #5363 I noticed this happening when making some changes on the nextjs.org/learn app. Basically we didn't apply updates when a warning was emitted from webpack. This would cause issues for users using eslint-loader or similar too.		2019-01-21 22:39:39 +01:00
..
app-aspath	Fix linter (#5350)	2018-10-20 17:00:01 +02:00
app-document	Fix #5674 Append crossOrigin on the client side too, add config option for crossOrigin (#5873)	2018-12-13 01:05:21 +01:00
babel	Fix linter (#5350)	2018-10-20 17:00:01 +02:00
basic	Make HMR still apply updates when there is a webpack warning (#6099)	2019-01-21 22:39:39 +01:00
cli	Remove node-args in favor of NODE_OPTIONS environment variable (#5910)	2018-12-17 19:17:29 +01:00
config	Added WebSocket arg to allow manually setting port (#5963)	2019-01-01 01:07:10 +01:00
custom-server	Remove next/asset (#6046)	2019-01-14 01:32:20 +01:00
dist-dir	Fix linter (#5350)	2018-10-20 17:00:01 +02:00
export	Remove /asset from exportPathMap (#6053)	2019-01-14 15:32:55 +01:00
filesystempublicroutes	use native http instead of micro (#5706)	2018-11-19 16:36:18 +01:00
ondemand	Implement websockets based on-demand-entries ping (#4508)	2018-12-14 12:25:59 +01:00
page-extensions	Fix linter (#5350)	2018-10-20 17:00:01 +02:00
production	Make sure 404 is rendered (#5880)	2018-12-13 19:46:16 +01:00
production-config	Add test for generateBuildId (#5816)	2018-12-04 16:42:25 +01:00
serverless	Export render instead of default for serverless target (#5979)	2019-01-02 14:59:28 +01:00
size-limit	Add new limit for size	2019-01-11 23:57:38 +01:00
with-router	Fix linter (#5350)	2018-10-20 17:00:01 +02:00