The problem is, all the issues and PRs are being logged here.
Should npm be pointing to this repo, or should we be logging issues on @garcimouche's fork?
Also, I haven't seen any responses to the issues that are being opened here. As a user of this karma plugin that has created a tutorial on and given talks on how to use it, as well as created a yeoman generator based on it, I think the issues recently raised around replacing the outdated copy of the dojo loader source code in this repo by registering dojo as a dependency (#6 and #7) and allowing users to specify the location of their own dojo loader (#5) are important improvements that will make this plugin much more useful. If you want someone to help bring those ideas into this repo and help maintain it, I'd be glad to be made a contributor collaborator.
@garcimouche and @vojtajina
I just realized that karma-dojo on npm is pointing to https://github.com/garcimouche/karma-dojo (which is a mirror of this one).
The problem is, all the issues and PRs are being logged here.
Should npm be pointing to this repo, or should we be logging issues on @garcimouche's fork?
Also, I haven't seen any responses to the issues that are being opened here. As a user of this karma plugin that has created a tutorial on and given talks on how to use it, as well as created a yeoman generator based on it, I think the issues recently raised around replacing the outdated copy of the dojo loader source code in this repo by registering dojo as a dependency (#6 and #7) and allowing users to specify the location of their own dojo loader (#5) are important improvements that will make this plugin much more useful. If you want someone to help bring those ideas into this repo and help maintain it, I'd be glad to be made a
contributorcollaborator.