Christopher Hiller

A new interface may be the best way to go, because you have several interfaces this would need to be implemented in. But, if this was going to be done,...

There's really no way to automatically provide a function to all interfaces; everything has to be explicitly placed in the context. This would actually _not_ be that trivial without some...

Two changes to above: - As per @mykola-mokhnach we will not be including `node-simctl`. - Include `ios-test-app` Progress is in [the new appium-ios monorepo](/appium/appium-ios), where I am mostly battling with...

@turadg re: packages linted individually. I have a feeling it will actually be significantly more performant to run it once from the workspace root; not because of ESLint proper, but...

I confirmed with one of tseslint's maintainers that my intuition about compilation was correct; tseslint needs to compile not only the individual workspace "under lint", but _also_ each workspace in...

There's probably more work that can be done here, but it's fast enough for now. Closed by #2877

> A negative side-effect of this change is that modules under the anonymous package.json would not be able to find any of their dependencies. In Node.js, this is not a...

@kriskowal But anyhow, the more correct solution is what you suggested: "inherit" from the parent `package.json`. There seem to be some helper functions. > I could also imagine solving this...

This is tricky. On the one hand, it _looks like_ we should be able to treat the parent and any "anonymous" package in its scope as a single Compartment, and...

> A package.json that consists solely of the module type specification (and is lacking name most importantly) we don't take it into account as a package descriptor at all. We...