You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
practicalmeteor:mocha-core hasn't been maintained since June 2016, It may be worth preventively updating the packages there.
It's not a big package, and I'm not sure if the separation of concerns is critical in this case. It may be worth incorporating it here. For example: Some features such as grep, or custom reporters would need patching to the practicalmeteor:mocha-core code.
The text was updated successfully, but these errors were encountered:
I collaborated with them on that package, and we need to use the same core package as practicalmeteor:mocha in order to avoid dependency issues when your app uses both drivers. I'd like to discuss with the practicalmeteor guys possible moving all of these test packages into a "testing" org or something like that so that we can maintain them all together.
One thing we could look at doing is to make mocha NPM package a peer dependency, in which case the mocha-core pkg will likely never need any updating unless the mocha API changes.
practicalmeteor:mocha-core hasn't been maintained since June 2016, It may be worth preventively updating the packages there.
It's not a big package, and I'm not sure if the separation of concerns is critical in this case. It may be worth incorporating it here. For example: Some features such as grep, or custom reporters would need patching to the practicalmeteor:mocha-core code.
The text was updated successfully, but these errors were encountered: