by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 10 08:48
    dependabot[bot] labeled #80
  • Sep 10 08:48
    dependabot[bot] opened #80
  • Sep 10 08:48

    dependabot[bot] on npm_and_yarn

    Bump http-proxy from 1.18.0 to … (compare)

  • Sep 09 17:04
    dhartjes commented #73
  • Aug 26 17:51
    panta82 commented #73
  • Aug 26 17:50
    panta82 commented #73
  • Aug 26 17:32
    Jack-Barry commented #73
  • Aug 26 17:06
    panta82 commented #73
  • Aug 26 17:02
    Jack-Barry commented #73
  • Aug 26 16:45
    Jack-Barry review_requested #72
  • Aug 24 04:14
    techmunk commented #78
  • Aug 20 20:02
    panta82 commented #73
  • Jul 31 11:52
    dependabot[bot] labeled #79
  • Jul 31 11:52
    dependabot[bot] opened #79
  • Jul 31 11:52

    dependabot[bot] on npm_and_yarn

    Bump elliptic from 6.5.1 to 6.5… (compare)

  • Jul 29 21:27
    Jack-Barry commented #9
  • Jul 29 17:24
    lakeshadow0 commented #9
  • Jul 29 17:24
    lakeshadow0 commented #9
  • Jul 29 17:19
    lakeshadow0 commented #9
  • Jul 29 16:53
    lakeshadow0 commented #9
Victor Vlasenko
@larixer
what problem?
Supremeo
@supremeo
hi victor
its not detecting changes
so basically need to kill the term and run again
using mix-laravel and vue
Victor Vlasenko
@larixer
what version of mochapack do you use ? 1.1.1 ?
Supremeo
@supremeo
"mochapack": "^1.1.1",
yep
"test:watch": "mochapack --watch --webpack-config=node_modules/laravel-mix/setup/webpack.config.js --require tests/JavaScript/setup.js tests/JavaScript/**/*.spec.js",
Victor Vlasenko
@larixer
can you try "mochapack": "1.1.0" ?
Supremeo
@supremeo
sure
Victor Vlasenko
@larixer
I have made related changes to watching in 1.1.1, maybe I have broken something
Supremeo
@supremeo
no.. doesn't seem to be it
i suspect it's not playing nicely with docker perhaps
Victor Vlasenko
@larixer
maybe, but maybe you don't read docs :)
the globs must be in double quotes
I'm not 100% sure, this is the reason, but it very well might be
Supremeo
@supremeo
oh wow
how did i miss that
let me try
weird because the test runs... It just doesn't watch
You should consider throwing a warning for semi-blind people like me :)
Victor Vlasenko
@larixer
well, I can't, because your shell might unroll globs and mochapack sees final result
Supremeo
@supremeo
no diff...
can you verify this format please
"test:watch": "mochapack --watch --webpack-config=node_modules/laravel-mix/setup/webpack.config.js --require tests/JavaScript/setup.js \"tests/JavaScript/**/*.spec.js\"",
Victor Vlasenko
@larixer
yes, the format is correct
well, I have no other clues, I need some example to reproduce myself
Supremeo
@supremeo
do you have any experience with laravel-mix ?
Victor Vlasenko
@larixer
no, I have no
Supremeo
@supremeo
so mix is a wrapper for webpack
Victor Vlasenko
@larixer
if you could set up some minimalistic project on github or point me to it, I can try to reproduce myself and look whats wrong
Supremeo
@supremeo
i suspect it's not emitting changes
Ok thanks Victor, I'll try to work it out, if not make a repo. It's not a high priority though. I'll report back if I resolve it in case you care to know
thanks for the help
Victor Vlasenko
@larixer
sure, thank you !
cooperate
@cooperate
Hi there
Victor Vlasenko
@larixer
Hi
Rohde Fischer
@rfftrifork
is there a way to pass the mocha --files argument through mochapack?
Victor Vlasenko
@larixer
@rfftrifork No, more context can be found here:
sysgears/mochapack#34
Relevant mocha issue:
mochajs/mocha#4122
Rohde Fischer
@rfftrifork
@larixer thanks. That explains why I couldn't find anything in the docs xD But yeah, I think that's a quite important feature to have
Victor Vlasenko
@larixer
Yes, but if mocha team will not collaborate, we can do little to resolve this
Rohde Fischer
@rfftrifork
ah bummer, is it possible to to utilize the mocha.opts feature somehow?
Rohde Fischer
@rfftrifork
oh, I got the impression that those opts was for mochapack and not mocha?
Victor Vlasenko
@larixer
yes, its for mochapack, so it won’t solve your issue
Rohde Fischer
@rfftrifork
ah ok, but if mocha is nicely behaved, I guess it should read mocha.opts, and I guess an option for mochapack could be to utiliza that for people who need more configurability? If you add a --mochaOpts parameter that passes on to mocha's --opts, wouldn't you then have a workaround intil mocha decides to exposes yargs?
Victor Vlasenko
@larixer
Maybe, I have no idea to be fair, it needs to be investigated
Its worth to leave a comment about this idea here:
sysgears/mochapack#34