Updating build process to create .d.ts declaration files

[landonxjames]

Updating build process to create .d.ts declaration files so jco is usable as a library in a typescript project.

The changes to enable this:

• Add a minimal tsconfig.json to generate ts types from the JSDoc comments. See the ts docs for more info about the configuration.
• Update the package.json build script to run tsc
• Update .gitignore to ignore the new .d.ts and .d.ts.map files which are generated in the src/ directory.
• Add new option to --no-namespaced-exports to jco to prevent generating exports like test as "test:flavorful/test" which are not currently compatible with typescript. See Support “Arbitrary module namespace identifier names” microsoft/TypeScript#40594

Resolves #168.
Resolves #253

[guybedford]

Rather than doing this via replacement (since if jco has this issue itself then other libraries built with jco will too), perhaps we should instead make it a transpile option to omit these names?

Perhaps something like --ts-compat or --no-namespaced-exports. Would you be interested in working on a patch along those lines here?

[landonxjames]

Yep happy to take a look at that (and fix this windows build issue). Will probably take me a few more days or through the weekend, but any pointers to that section of the code (and potentially how cli options flow from the js to the rust bits) would be appreciated

[guybedford]

Sure, the exports are output by the "esm bindgen" render routine in https://github.com/bytecodealliance/jco/blob/main/crates/js-component-bindgen/src/esm_bindgen.rs#L184.

[landonxjames]

Alright updates are made and the --no-namespaced-exports option has been added

[guybedford]

Great work, thanks for adding this.