Following on from the discussionstarting here in the chat.

Mithril's internal ospec is deprecated andconsole.warns to this effect on execution, recommending the canonical npm install ofospec. However, installing this as directed doesn't override Mithril's binary path binding for its internal ospec. From my tests, whichever is installed first, installing bothmithril &ospec always results in the Mithril's ospec binding taking precedence;@orbitbot says he is able to get ospec to take precedence based on installation sequence, but I couldn't replicate.

The issue of conflicting binary path registrations in npm package dependencies has been raised at least a couple of times (npm#7130 &npm#9040) but the trail has run cold seemingly without resolution.

I've raised a discussion on the npm Github org feedback site – but maybe I ought to revive one of the issues above or file a new one?

In the meantime we might be able to advise a hack to account for the current deprecation warning's failure. 🤔