-
-
Notifications
You must be signed in to change notification settings - Fork 121
Update package.json for working with ESLint 5 #231
Conversation
Travis is failing: |
Ah - the Travis failures seen here are unrelated to the ESLint 5 upgrade, but are instead due to a change in webpack output between webpack ...and this repository doesn't have a lockfile, so Travis is just pulling in latest (and there have been no landings on The expected output just needs updating. IMO this is a good example of why even libraries/consumable packages should still have lockfiles - and then use tools like https://renovatebot.com/ to automatically refresh them on a schedule - since it would give a failing "refresh lockfile" PR with easier to deduce cause. |
I've opened PR #235 to fix the unrelated test failures seen here. |
…-contrib#235) Since the error output format changed in webpack/webpack#6542 to prefix the error with the loader name. Now the tests use the original `error.message` (which is unchanged), rather than the adjusted `message`. Fixes webpack-contrib#233.
Can you rebase your pr on master so tests go green? thanks |
Also please update dev deps so we are sure it's ok. |
@MoOx now ok? |
No, sorry. You have merged back master which give a weird thing... |
Closed for #240 |
ESLint 5 released, changed peerDependencies to higher version