TypeScript support

I’m using Leaflet.GeometryUtil in a TypeScript project. As far as I’m aware, there are no typings yet, as mentioned in #73.

I would like to write some typings. There are 3 options:

1. Write typings and publish them as a separate @types/leaflet-geometryutil package.
2. Write typings and include them in this repository. This would involve creating a .d.ts definition file and referencing it in the "types" field in package.json.
3. Convert the whole source code to TypeScript. This would involve changing the setup a bit. A build script would have to be run before publishing the project.

The first option is the least intrusive to this project, the third one is the most proper one, since it makes sure that the type definitions are really in sync with the code.

Which one would you prefer?

[IlyaDiallo]

I tend to prefer TS as well (let’s be honest, I deeply hate JS), but I’m not a maintainer of this package yet I’m a colleague of them. Converting everything is a risk to create new bugs, and let’s be pragmatic, just adding the typings would be the easiest solution. Converting to TS is a language and paradigm change, for the whole package, thus all package maintainers must agree altogether to do such a breaking change.

Now the debate is opened. But let’s start small and easy. This wouldn’t disallow to switch to TS later, but this need to be evaluated with everyone first.

The JS vs TS debate is a bit like the C vs C++ debate. It’s pointless without context - JS is better for some projects, TS is better for others. I’d like to point out that this project is a plugin for a JS library itself included in JS applications. So having to “compile” from TS to use it, or (more importantly) having to know TS to contribute to it would be a huge drawback. TS coders are supposed to be familiar with JS but not the other way around.

[cdauth]

That makes sense.

Also, once the typings are there, it’s less work to convert the existing code to TypeScript.