fix generating TypeScript type definitions

[endel]

Hi @martenrichter,

I've made some changes to tsconfig.json and changed to generate type definitions only before publishing (prepublishOnly)

I'm still getting used to the codebase, let me know if I'm missing something.

Before

After

---

All the best and happy new year ✨

[martenrichter]

Also happy new year to you! (In a couple of hours I suppose).
Regarding the change, I actually would like to keep the "types" command, so that I can verify, that the types are ok, before I hit
The rest I will comment within the commit.

[martenrichter]

Does this generate a problem? The version release today, does it still have problem with types?

[endel]

Just checked the version of today (1.0.8) and #233 still persists due to the path to ./dist/lib/index.d.ts that is failing.

A potential solution could be pointing "types": "./dist/main/lib/index.d.ts", but I believe having both projects compiled under dist was not intentional.

Below is a screenshot of both modules (1.0.8) after being installed via NPM (@fails-components/webtransport and @fails-components/webtransport-transport-http3-quiche), you can see both projects have the same output under dist folder, whereas they should only contain their own output (which this PR addresses):

[martenrichter]

Ok, the screenshots match my development environment.
Yes, it was not intentional.
But I had to trouble with the crossreferencing of the two packages in types.
Does a run of tsc --build at workspace level run fine with your changes?

[martenrichter]

Please look also at the github action for the actual publishing...

[endel]

Thanks for the review, I've just updated bringing back the "types" script and removing the prepublishOnly, I believe publishing should work as before now 🙌

[martenrichter]

Ok, I will then hit the CI/CD jobs to see if they run, and maybe merge it later. I will probably wait for a release (or do the types not work at all?) until another issue pops up.