#2935 Remove the .d.ts file and rely on JSDocs entirely

[mayankkamboj47]

When we import values in a Typescript project, Typescript automatically infers the types using JSDoc comments if possible: https://www.typescriptlang.org/docs/handbook/intro-to-js-ts.html#providing-type-hints-in-js-via-jsdoc. The present index.d.ts file is then just a redundancy on top of the Eleventy.js file, and requires additional maintenance to keep it up to date.

This fixes #2935

[zachleat]

I’d love to follow Svelte’s lead here and simplify things! cc to @Ryuno-Ki for their take too

[mayankkamboj47]

@zachleat Can you elaborate ? I checked svelte's repo and they seem to be using a mixture of jsdoc and .d.ts files. Also tagging @Ryuno-Ki for their thoughts

[zachleat]

@mayankkamboj47 sveltejs/kit#4429 (comment) has some info. I think the Svelte(Kit?) maintainers infamously chose JSDoc over full TypeScript awhile back.

[uncenter]

I think .d.ts files are different than using TypeScript though.
https://github.com/search?q=repo:sveltejs/svelte%20path:*.d.ts&type=code

[zachleat]

Merged with a few additions, thank you! Readded jsdoc to the npm scripts @Ryuno-Ki (though it’s .npmignore’d too) and I believe the goal here is to document the supported user-land configuration API (Eleventy.js and UserConfig.js)