-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is mocha-webpack still maintained? #289
Comments
It looks like @zinserjan hasn't been active on github (or anywhere else?) since early may 2018... I hope they are ok! we've been using the 2.0.0-beta.0 version and it works reasonably well, but it would be great to get a release out on NPM. At what point does someone request to take this over on NPM? |
@alecf Thanks for reply. I hope @zinserjan are well too! Yes, |
I'd vote to call it mocha-webpack-4 |
Hey guys, Webpack 4 has been out since March, and I need to get this project working again. Has anyone forked this, and updated for Webpack 4? @zinserjan If you still get these notifications, would you consider moving mocha-webpack over to the webpack-contrib repo? (similar to karma-webpack) |
@notyoyoma The latest version |
@notyoyoma It doesn't mean though that the project is not working for Webpack 4. And it doesn't mean that debugging has ever worked the way you want it to. |
@Vlasenko I will look again, and try to get the debugger working as described here, but I have already spent ~20hrs on this problem over several weeks, and am fairly certain the problem lies with mocha-webpack. Regardless, there still has been no response or activity from zinserjan in the last month. Does anyone know if he has a twitter or other social media presence? I've looked but haven't found anything. If he doesn't return, we may need to fork the project to continue development. |
I'd be thrilled if someone with the nescessary expertise would resurrect this project. I've been experimenting with |
A dependency in DepShield reports that this application's usage of lodash.debounce:4.0.8 results in the following vulnerability(s): (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)
See #297 |
@darrynten Yeah, looks like we are one step closer to the need of forking this repo and maintaining the fork.... |
Hey everyone! I have created the fork of this repository named I and my team is going to maintain it, until we see any activity from original author. Nothing too heavy - we will do security updates mostly and accept pull requests. The first version is published into npm |
Thank you so much! I can confirm
|
@zinserjan Thank you for the great work on a great tool!
Let me kindly ask a straight question, is
mocha-webpack
still maintained?It looks strange that Pull Requests from contributors starting from end of March do not get any reaction from you and that many greenkeeper PR's and issues hang around, no new commits being pushed... It looks like as if project was abandoned from some reason.
Could you shed some light for your users?
Many thanks!
The text was updated successfully, but these errors were encountered: