It seems we simultaneously treat the SDK as a package and as a project:
Package: we don't run npm install inside its folder, it's installed indirectly through the root package.json)
Project: We run tsc inside.
I can't remember exactly whether this is the case, but I'm 80% sure. We should double-check before further digging in. If that's the case, devDependencies may behave unexpectedly.
This is wrong and might be related to the problem described in #2085.
It seems we simultaneously treat the SDK as a package and as a project:
tscinside.I can't remember exactly whether this is the case, but I'm 80% sure. We should double-check before further digging in. If that's the case,
devDependenciesmay behave unexpectedly.This is wrong and might be related to the problem described in #2085.