Mocha-webpack does not appear to work with webpack 4

[ctaylo21]

Issue
Running mocha-webpack with the latest webpack 4 appears to fail. No test output is displayed.

I have create a repo that recreates the issue here: https://github.com/ctaylo21/mocha-webpack-webpack4-bug

I see a deprecation warning about DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead but from what I've read that shouldn't be a breaking change.

Any way to debug this to see if something is blowing up and the error just isn't getting output anywhere?

[astorije]

If anyone wants to help, I opened a PR at #211, solely counting on CI reports to tell me if things are working smoothly 😅

[kiaking]

Super nice attempt there! I would really love to see mocha-webpack support webpack 4 and (mocha 5).

But even if your PR gets working, would it be merged and published? Seems like this project has stopped for a while... I'm concerned on that more than the PR.

/Cc @zinserjan

[astorije]

@kiaking, I wouldn't be too worried about this, because there are ways to solve this: fork the project, contact @zinserjan by some other means to kindly ask for his attention, ask him to add maintainers to the project, etc.

And even if that doesn't happen, once support for Webpack v4 is ensured, one can always use the GitHub URL in their package.json until this gets released or forked. Not ideal, but I'll take this over not being able to upgrade Webpack at all :)

About this PR, I'm unfortunately stuck and could use some help. If you or anyone else is willing to help, I am happy to grant access to my branch for people to play with, or apply changes if you have any to suggest!

🙏 🙏 🙏

[kiaking]

Wow and see what happened. New release was published!!! Yeah!!! 🎉

I would really love to help, I do but I just don't have enough time... But if I can find any, I will for sure!

[kraenhansen]

👍 for the release, although that doesn't seem to fix this issue. @astorije I'm cheering for you (or anyone else that can help move this along)!

[adonespitogo]

Thanks for working on this @darrinholst . Really wanted to work on this. But looking at the huge pile of codes, couldn't figure out where to start as I have not worked on any webpack plugin before. @astorije Can you point me to the right direction?

[astorije]

@adonespitogo, there is current work on this and @zinserjan is almost done! Props to him!!

[adonespitogo]

Thanks @astorije and to @zinserjan . Really looking forward for this to work. Kudos to you guys!

[adonespitogo]

Wow that was fast 🎊 Thanks so much for the hard work you guys put on this. Looking forward for the release 😃

[adonespitogo]

@zinserjan

I tried to use the newly merged PR for webpack 4 support in master branch. When I attempt to run my tests, I get this error:

module.js:559
    throw err;
    ^

Error: Cannot find module '../lib/cli'
    at Function.Module._resolveFilename (module.js:557:15)
    at Function.Module._load (module.js:484:25)
    at Module.require (module.js:606:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/adonesp/Projects/espresowifi/node_modules/mocha-webpack/bin/mocha-webpack:2:1)
    at Module._compile (module.js:662:30)
    at Object.Module._extensions..js (module.js:673:10)
    at Module.load (module.js:575:32)
    at tryModuleLoad (module.js:515:12)
    at Function.Module._load (module.js:507:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! piso-wifi@3.0.3 test: `mocha-webpack "test/**/*.spec.js"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the piso-wifi@3.0.3 test script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/adonesp/.npm/_logs/2018-03-18T22_55_35_622Z-debug.log

[zinserjan]

Installing from github doesn't work. You need to build the sources with npm run build ;)

[adonespitogo]

Can I build the sources with github as a source? If so, how? Sorry really need this to work badly. What is your ETA for the next release?