Filip Sodić

Related to #2053

Closed by #2375

@infomiho Yes. Well, at least to me :smile: If you know the answer, you can close it.

Another use mentioning this as a problem: https://discord.com/channels/686873244791210014/1287813207297359987/1289291579206668298

Another one: https://discord.com/channels/686873244791210014/1289650697494728787/1290327971852189749

> First two points relate to the pull_request_template.md or something else? I was thinking exclusively of instructions in `waspc/README`, but the `pull_request_template` is a good idea too!

I like the analysis @FranjoMindek! Some of the options are bundled together. For example, where the app runner lives in and how we distribute it are related but distinct issues....

From what I understand, the NPM approach makes sense. But before we dive into it, let's make sure we answer some questions from before. Specifically, this one: > One thing...

> It seems to be related to ts-node which jest uses under the hood to resolve the tsconfig.json. That's not it (at least I think it isn't). `ts-node` is nowhere...

Next time this happens, we should ask our users for a zip of their projects (or at least their `package.json` and `package-lock.json` files).