[lit-starter-ts] Output files into a directory instead of top level

[darvid7]

Hey all,
I think I jumped the gun with lit/lit-element-starter-ts#10, my rationale was outputting files to the top level dir seems harder to maintain and can pollute your workspace when you run npm run build. At the very least it will mean.

• you need to add 4 items to your .gitignore for every .ts file in your src
• you top level dir in your workspace gets bloated

I think that is enough reason to want to output the transplied ts into another directory like /build.

We're intentionally putting output files in the top level, as one might if you were writing that JavaScript directly without TypeScript. Placing files in /build simply exposes that there is a build.

I'm not sure im sold on this reasoning since this is a TS starter repo and I don't think people would want to write raw js here.

Would love your thoughts!

[arthurevans]

I think @justinfagnani meant that an end user of a published package shouldn't need to be aware of whether it's written in TypeScript or JavaScript.

[justinfagnani]

Yep ^

[arthurevans]

I think there are some valid concerns here. The .gitignore and clean script both get kind of gnarly (and would be nigh unmanageable if you had a bunch of TS files).

[arthurevans]

Could have a top-level static index.js (or my-element.js) that just imports build/my-element.js, then the user wouldn't need to think about where it was coming from...