Clearer structure/instructions for Typescript projects

[Frozenreflex]

Preface, I'm not very familiar with the Javascript, NPM, Typescript, or Bangle ecosystems, and got some help from some other people to get a project template set up. I'm a C# programmer, and I prefer static typing, so Typescript seemed like a good solution.
In that process of getting help with setting up a project, the others said that the way that the Typescript bindings are set up is strange, if they're to be used for individual projects. They also mentioned that it's set up to build every Typescript project in the repo, which makes it sound to me like the Typescript bindings were made to be used for the web app backend rather than for building individual projects. If that is the case, could there be some sort of method set up to make it easier to use Typescript in standalone projects, such as an npm package? In my case, I'm going to write my apps using WebStorm locally, compile to JS, then upload to the watch using the web IDE, and it would be much easier to include an npm package than to clone the entire repo and copy just the types folder (which ended up being the solution I'm going with for now)

[bobrippling]

Yes - at the moment a single typescript build will build all the apps, which share the same namespace (for example, multiple boot apps will all run at the same time, as will widgets).

Typescript bindings (I'm presuming you mean the shared types) aren't for the web app backend - they're for the watch apps themselves.

If you have any useful changes or notes from getting your local setup going, even if it's specific to WebStorm, that'd be great - I can find where we can add them, either here or in the docs.