-
-
Notifications
You must be signed in to change notification settings - Fork 52
Mark mocha@6 compatibility and upgrade all dependencies #76
Conversation
- fixed lint warnings in EnhancedMocha.js - updated bundle snapshot
@michael-ciniawsky, any chance you could check this out? :) |
Upgraded to css-loader@2.0.1. any chance someone reviews this? perhaps @evilebottnawi? |
Someone? Anyone? |
switch to @webpack-contrib/defaults
Updated dependencies once more. Would be awesome if this could be reviewed/merged/released. |
@TheLarkInn heya! any idea who do I need to mention for this to get reviewed? :) |
@evilebottnawi thx for reviewing. any chance to get a release with these dep upgrades? |
This is frustrating. 😞 |
Ping? |
Any chance this could merged? It's causing a lot of un-needed dependencies down the line. |
Currently we have no active maintainers for this project. if somebody want to help us with |
Both I and @tomrav are willing to keep this one maintained. |
@AviVahl do you have rights on merge and release (github/npm)? |
@AviVahl send invite, please ping me when you accept |
Awesome. Accepted. |
I do. Thanks. My npm user: avi.vahl |
@AviVahl Can't add to npm (they still can't fix bug around adding users - |
Just ping me when all will be done |
Updated all |
npm@6.4.1 has a bug when generating lock file from scratch. it generates a lock file, and then a second run adds "optional" fields. newer npm fixes this issue.
Looks good to me. 👍 |
@evilebottnawi squashed to master. (accidentally omitted the |
👍 |
@webpack-contrib/defaults
This PR contains a:
Motivation / Use-Case
css-loader@2 came out and uses postcss@7.
Breaking Changes
css-loader
has breaking changes, but it is only used to loadmocha
's css here, so nothing breaking is expected.Additional Info