-
Notifications
You must be signed in to change notification settings - Fork 220
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 this abandonware? #138
Comments
The javascript world is moving fast and dependencies become fragile. It seems karma-webpack is unable to keep up. |
Maybe we can collaborate with the original owner to resolve any issues? It's open source after all and if we use it we should try to support it. I'm willing. |
@necolas @bbottema @stevegibbings - As of this afternoon, all of the loaders have been assigned project leads and contributors to take the load off the webpack core team. The karma-webpack lead is @MikaAK, I am one of the contributors that will be assisting Mika. I have a bit of documentation to take care of in #139 and need to get our validation up to the webpack/webpack standard in #140. The intent is to get this done and a PR open this weekend, full test coverage may not happen that fast but stranger things have happened. As soon as that is complete, we will be working through backlog in the following in order.
|
@d3viant0ne great news. What's the best way I can assist? |
It's really up to @MikaAK That said, give us a few days to get the docs and code validations in place and I'm sure Mika will start sorting & prioritizing issues. That is probably going to be the point where community involvement is going to be most helpful. I just wanted to take a moment to comment as I was creating working tasks to assure everyone that we will be getting this loader squared away in short order. |
Understood and it's all appreciated. I'll support you guys wherever I can. |
Good to know this is still alive. Keep up the good work. |
Good to hear. Thank you! |
There hasn't been a new version published for a year
The text was updated successfully, but these errors were encountered: