If package A depends on package B which depends on package C, then I expected A’s package.json to only list B in its dependencies and yet still be able to load B successfully because I expected RunKit to walk the poset of dependencies, discover C, and ensure it’s available before launching A.
Is this not preferable?
Otherwise A has to include the closure of all its dependencies to get RunKit support even though locally its not required as NPM installs the closure for me.
Oh, my bad… I didn’t see that it was a different linq package bringing in define-generator. You’re right RunKit should (and will) crawl the dependencies, however linq.concat also doesn’t include genie-generator as a dependency (only a devDepenedency): https://npm.runkit.com/@kingjs/linq.concat/package.json?t=1534448173175