Thanks <@U0BMF6PDJ> ! I see 4 points here: 1) Pub...

# javascript

[maballesteros]

Thanks @bashor ! I see 4 points here:

1) Publish a community repository as DefinitelyTyped did for TypeScript
- This can be done right now
- This should be done ASAP, so Kotlin JS gets traction in the community as an interesting alternative to already existing options

2) Create the typings, and publish them in the repo. This could be done:
- Manually: PROS (Can be started right now. Can exploit Kotlin sugar not easily inferred from d.ts) CONS (It's a hard work)
- Automatically: PROS (Best reuse of existing assets) CONS (It requires to KT-2970 be done... when?)
- Mixed: start manually, then add automation when available

3) Handle dependency management. Here's wher Maven and such pays the bill. You could create a repo and allow people to just "copy" the definitions, but it can be done much better with Maven.

4) Improve dependency management, allowing the inclusion of additional resources (original .js file and attached CSS/imgs/etc. files)
- I've tried WAR overlays as a workaround and I didn't like the result
- ...so +1 to KT-6463

With https://github.com/kotlin-es/kotlinjs-typings we tried to solve 1), 2), and 3) as we didn't find alternative.

So, what would you recommend us? Should we discontinue those initial steps?

Thans in advance!