Mocha-webpack does not appear to work with webpack 4 #209

ctaylo21 · 2018-02-26T20:20:27Z

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?

The text was updated successfully, but these errors were encountered:

astorije · 2018-03-09T05:47:29Z

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 · 2018-03-16T05:59:48Z

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 · 2018-03-16T06:12:46Z

@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 · 2018-03-16T16:18:32Z

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 · 2018-03-16T19:54:39Z

👍 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 · 2018-03-18T13:49:18Z

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 · 2018-03-18T16:22:20Z

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

adonespitogo · 2018-03-18T20:56:56Z

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

adonespitogo · 2018-03-18T22:47:18Z

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

adonespitogo · 2018-03-18T23:00:27Z

@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 · 2018-03-18T23:05:22Z

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

adonespitogo · 2018-03-18T23:12:04Z

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?

adonespitogo · 2018-03-18T23:27:20Z

I was able to build the sources by forking the master branch and ran npm build then copy the sources to my local node_modules directory. Now I'm having another error:

> mocha-webpack "test/**/*.spec.js"

WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration has an unknown property 'optimization'. These properties are valid:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
   For typos: please correct them.
   For loader options: webpack 2 no longer allows custom properties in configuration.
     Loaders should be updated to allow passing options via loader options in module.rules.
     Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
     plugins: [
       new webpack.LoaderOptionsPlugin({
         // test: /\.xxx$/, // may apply this only for some modules
         options: {
           optimization: ...
         }
       })
     ]
    at webpack (/home/adonesp/Projects/espresowifi/node_modules/mocha-webpack/node_modules/webpack/lib/webpack.js:19:9)
    at createCompiler (/home/adonesp/Projects/espresowifi/node_modules/mocha-webpack/lib/webpack/compiler/createCompiler.js:15:40)
    at TestRunner.<anonymous> (/home/adonesp/Projects/espresowifi/node_modules/mocha-webpack/lib/runner/TestRunner.js:164:51)
    at eval (eval at processIncludes (/home/adonesp/Projects/espresowifi/node_modules/mocha-webpack/node_modules/nodent-runtime/runtime.js:36:12), <anonymous>:3:4727)
    at <anonymous>
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! 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-18T23_24_43_851Z-debug.log

I guess I just have to wait for the next release. Thanks so much for your work @zinserjan

zinserjan · 2018-03-19T01:03:43Z

Just tried to release it as pre-release... But that failed cause npm run docs:prepare gives me some peerDependencies failures instead of warnings...
Error: The package eslint does not satisfy its siblings' peerDependencies requirements!

This needs to be fixed before I can release it.

astorije · 2018-03-19T01:40:42Z

@zinserjan, this is what I was talking about at #211 (comment). I'll look into it tonight :)

zinserjan · 2018-03-21T21:30:58Z

Released as 2.0.0-beta.0

astorije · 2018-03-22T00:08:52Z

Just started using it in thelounge/thelounge#2117, and so far so good, it seems.

yinsang · 2018-03-25T02:54:18Z

yarn upgrade mocha-webpack@v2.0.0-beta.0
or
npm install mocha-webpack@next

ezmiller · 2018-04-23T15:19:59Z

Upgrade to 2.0.0-beta.0 fixed this for me. Thanks @zinserjan!

markerikson · 2018-04-27T20:29:55Z

It appears that this update to work with Webpack v4 made mocha-webpack incompatible with Webpack 3, due to the change in importing Webpack's watching compiler:

Error: Cannot find module 'webpack/lib/Watching'
    at Function.Module._resolveFilename (module.js:555:15)
    at Function.Module._load (module.js:482:25)
    at Module.require (module.js:604:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\myproject\node_modules\mocha-webpack\lib\webpack\compiler\createWatchCompiler.js:21:17)

Can this be handled in a way that's compatible with both Webpack 3 and Webpack 4, or are all the other Webpack 4 changes too much for it to work with both?

PandaWood · 2018-05-04T04:02:16Z

I'm slightly confused, the doco at http://zinserjan.github.io/mocha-webpack/ claims that mocha-wepback works with webpack v4.x.x but this thread suggests it won't and I'll need 2.0.0-beta.0 ...?

I've just discovered the project and using WebPack v4

adonespitogo · 2018-05-04T04:07:02Z

@PandaWood support for webpack 4 is in beta 2.0.0 that's why you need to install the beta in order to use it with webpack 4.

a1mersnow · 2018-05-09T06:08:30Z

I update to mocha-webpack@next
But still not work

It just output nothing

nevercast · 2018-06-01T01:08:41Z

@aimergenge Can you check this again? It may have been resolved this week.

Currently, installing mocha-webpack via npm defaults to 1.1.0 which does not work with webpack 4 but the docs say otherwise. Updated readme so it is more explicit (zinserjan#209)

mbana · 2018-07-24T14:44:57Z

is this fixed?

vivaldus · 2018-08-23T04:59:19Z

I'm using webpack@4.16.5, mocha-webpack@2.0.0-beta.0 with command:

./node_modules/mocha-webpack/bin/mocha-webpack --webpack-config ./test/webpack.test-backend.config.ts ./src/**/*.spec.ts

with specs in webpack.test-backend.config.ts that run fine with plain old webpack. Below is the error I'm getting. Not sure what to make of this -- looks like an antiquated 'solution'. Any insights/suggestions would be appreciated.

WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration has an unknown property 'commonWebpackConfig'. These properties are valid:
   object { mode?, amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry?, externals?, loader?, module?, name?, node?, output?, optimization?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, serve?, stats?, target?, watch?, watchOptions? }
   For typos: please correct them.
   For loader options: webpack >= v2.0.0 no longer allows custom properties in configuration.
     Loaders should be updated to allow passing options via loader options in module.rules.
     Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
     plugins: [
       new webpack.LoaderOptionsPlugin({
         // test: /\.xxx$/, // may apply this only for some modules
         options: {
           commonWebpackConfig: …
         }
       })
     ]

jocabrera · 2018-10-08T19:49:59Z

@ctaylo21 to fix this warning
DeprecationWarning: Tapable.plugin is deprecated. Use new API on .hooks instead
I updated that
npm i -D karma-webpack@next

kraenhansen · 2019-01-10T14:16:09Z

@yinsang / @zinserjan - Is it time for a 2.0.0 release? :)

chulman444 · 2019-02-13T07:38:03Z

Do we need a new maintainer?

mocha-webpack 2.0.0-beta (npm link) was published last year and is still the latest version.

Came across this issue long ago, and same solution fixed it. npm i -D mocha-webpack@next.

mattbontrager · 2019-06-13T17:55:22Z

Resolved issue by removing mocha-webpack and installing mochapack.

Neha8482 · 2020-07-09T08:10:36Z

Can anyone please help me with this issue TypeError: mocha.useColors is not a function

WEBPACK Failed to compile with 1 error(s)

TypeError: mocha.useColors is not a function
at configureMocha (C:\Users\dell\AppData\Roaming\npm\node_modules\mocha-webpack\lib\runner\configureMocha.js:34:9)
at TestRunner.prepareMocha (C:\Users\dell\AppData\Roaming\npm\node_modules\mocha-webpack\lib\runner\TestRunner.js:139:48)
at C:\Users\dell\AppData\Roaming\npm\node_modules\mocha-webpack\lib\runner\TestRunner.js:193:36
at C:\Users\dell\AppData\Roaming\npm\node_modules\mocha-webpack\lib\webpack\compiler\registerReadyCallback.js:26:7
at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:33:10), :16:1)
at AsyncSeriesHook.lazyCompileHook (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\Hook.js:154:20)
at C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\lib\Compiler.js:304:22
at Compiler.emitRecords (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\lib\Compiler.js:499:39)
at C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\lib\Compiler.js:298:10
at C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\lib\Compiler.js:485:14
at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:33:10), :18:1)
at AsyncSeriesHook.lazyCompileHook (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\Hook.js:154:20)
at C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\lib\Compiler.js:482:27
at C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\neo-async\async.js:2818:7
at done (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\neo-async\async.js:3522:9)
at AsyncSeriesHook.eval [as callAsync] (eval at create (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\HookCodeFactory.js:33:10), :4:1)
at AsyncSeriesHook.lazyCompileHook (C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\node_modules\tapable\lib\Hook.js:154:20)
at C:\Users\dell\AppData\Roaming\npm\node_modules\webpack\lib\Compiler.js:464:33
at MemoryFileSystem.writeFile (C:\Users\dell\AppData\Roaming\npm\node_modules\mocha-webpack\node_modules\memory-fs\lib\MemoryFileSystem.js:328:9)

Neha8482 · 2020-07-09T08:13:34Z

Can anyone help me with this issue TypeError: mocha.useColors is not a function

KMarshland · 2020-07-22T19:50:45Z

@Neha8482 I fixed TypeError: mocha.useColors by downgrading mocha from 8.0 to 7.2

snolangps · 2020-08-13T00:07:41Z

yarn upgrade mocha-webpack@v2.0.0-beta.0
or
npm install mocha-webpack@next

@yinsang still didn't work with mocha 8.., last it worked with for me was mocha 7.2.0

maxbogue mentioned this issue Mar 10, 2018

Add at least one frontend test. maxbogue/debatewithdata#70

Closed

archco mentioned this issue Mar 13, 2018

Update webpack to v4.1.1 archco/moss-ui#96

Merged

zinserjan closed this as completed in 02864e2 Mar 18, 2018

kraenhansen mentioned this issue Mar 22, 2018

Reenabling tests realm/realm-studio#762

Merged

ctaylo21 mentioned this issue Apr 2, 2018

[TRACKING] Webpack 4 support FormidableLabs/electron-webpack-dashboard#58

Open

zetaraku mentioned this issue May 25, 2018

Webpack compiles but mocha isn't executed #260

Closed

timiscoding mentioned this issue Jun 14, 2018

Update version info in readme #270

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Mocha-webpack does not appear to work with webpack 4 #209

Mocha-webpack does not appear to work with webpack 4 #209

ctaylo21 commented Feb 26, 2018

astorije commented Mar 9, 2018

kiaking commented Mar 16, 2018

astorije commented Mar 16, 2018

kiaking commented Mar 16, 2018

kraenhansen commented Mar 16, 2018

adonespitogo commented Mar 18, 2018

astorije commented Mar 18, 2018

adonespitogo commented Mar 18, 2018

adonespitogo commented Mar 18, 2018

adonespitogo commented Mar 18, 2018

zinserjan commented Mar 18, 2018

adonespitogo commented Mar 18, 2018 •

edited

adonespitogo commented Mar 18, 2018

zinserjan commented Mar 19, 2018

astorije commented Mar 19, 2018

zinserjan commented Mar 21, 2018

astorije commented Mar 22, 2018

yinsang commented Mar 25, 2018

ezmiller commented Apr 23, 2018

markerikson commented Apr 27, 2018

PandaWood commented May 4, 2018 •

edited

adonespitogo commented May 4, 2018

a1mersnow commented May 9, 2018

nevercast commented Jun 1, 2018

mbana commented Jul 24, 2018

vivaldus commented Aug 23, 2018

jocabrera commented Oct 8, 2018

kraenhansen commented Jan 10, 2019 •

edited

chulman444 commented Feb 13, 2019

mattbontrager commented Jun 13, 2019

Neha8482 commented Jul 9, 2020

Neha8482 commented Jul 9, 2020

KMarshland commented Jul 22, 2020 •

edited

snolangps commented Aug 13, 2020

Mocha-webpack does not appear to work with webpack 4 #209

Mocha-webpack does not appear to work with webpack 4 #209

Comments

ctaylo21 commented Feb 26, 2018

astorije commented Mar 9, 2018

kiaking commented Mar 16, 2018

astorije commented Mar 16, 2018

kiaking commented Mar 16, 2018

kraenhansen commented Mar 16, 2018

adonespitogo commented Mar 18, 2018

astorije commented Mar 18, 2018

adonespitogo commented Mar 18, 2018

adonespitogo commented Mar 18, 2018

adonespitogo commented Mar 18, 2018

zinserjan commented Mar 18, 2018

adonespitogo commented Mar 18, 2018 • edited

adonespitogo commented Mar 18, 2018

zinserjan commented Mar 19, 2018

astorije commented Mar 19, 2018

zinserjan commented Mar 21, 2018

astorije commented Mar 22, 2018

yinsang commented Mar 25, 2018

ezmiller commented Apr 23, 2018

markerikson commented Apr 27, 2018

PandaWood commented May 4, 2018 • edited

adonespitogo commented May 4, 2018

a1mersnow commented May 9, 2018

nevercast commented Jun 1, 2018

mbana commented Jul 24, 2018

vivaldus commented Aug 23, 2018

jocabrera commented Oct 8, 2018

kraenhansen commented Jan 10, 2019 • edited

chulman444 commented Feb 13, 2019

mattbontrager commented Jun 13, 2019

Neha8482 commented Jul 9, 2020

Neha8482 commented Jul 9, 2020

KMarshland commented Jul 22, 2020 • edited

snolangps commented Aug 13, 2020

adonespitogo commented Mar 18, 2018 •

edited

PandaWood commented May 4, 2018 •

edited

kraenhansen commented Jan 10, 2019 •

edited

KMarshland commented Jul 22, 2020 •

edited