Consider JSDoc @import for non-exported types

[colinrotherham]

Hello 👋

Thought I'd share a little improvement added in TypeScript 5.5: JSDoc @import tag

Should prevent @typedef re-exporting private/internal definitions in #5157 by using @import instead

[romaricpascal]

Oh, that's nice, thanks for pointing that out and updating the existing @typedef 🙌🏻 . Is the PR in draft because you're expecting to make further changes?

[colinrotherham]

@romaricpascal No problem 😊

Nah only in "draft" because I've only rolled out @import within source code, it's good to go if you're happy. I was being nosey and hoped it might ease up the missing exports in 75e6e14

I'd recommend widely using @import as it preserves all the generics too, so no need for @template

Just pushed an extra commit to demonstrate

[romaricpascal]

Thanks for marking as ready for review. I'll approve the workflows and have a look Thursday or Friday, hopefully it'll play nicely with the TypeDoc config update (whose aim is to have the types we don't export in the doc so you'd know what shape an AccordionConfig is, for example).

Happy to take over updating the rest of the import() in types, as well. Would it be fine if they were pushed on your branch so we merged them all in one go?

I'd recommend widely using @import as it preserves all the generics too, so no need for @template

Just to confirm, is it this part of the commit that statement refers to, where you were able to drop the @typedef for HandlerFunction and the @template it required to keep it being a generics because we were now able to directly use EvaluateFuncWith via @import?

[colinrotherham]

Happy to take over updating the rest of the import() in types, as well. Would it be fine if they were pushed on your branch so we merged them all in one go?

Yeah go for it ✅

Just to confirm, is it this part of the commit that statement refers to, where you were able to drop the @typedef for HandlerFunction and the @template it required to keep it being a generics because we were now able to directly use EvaluateFuncWith via @import?

That's the one

Previously all generics needed to be re-declared via @template, now they just work

[romaricpascal]

Yeah go for it ✅

Cheers! I've rebased on main and the @import tag seems to play nicely with the updates we recently made to TypeDoc for listing more internal types in the review app.

I've also added a round of updates for the @typedef {import(...)} tags in other parts of our code. The @import syntax is pretty neat when importing multiple types from a single file (and showed a couple of places we were importing unnecessarily). I didnd't see any obvious @template ones to update but we can always fix those later if there are any.

Looking into this further, I'm thinking one of the effect of using @import for the sources will be that the info within JSDoc blocks will only compatible with TypeScript 5.5 and further (as older versions won't understand the tag). This means only people running TypeScript 5.5 will get the knowledge that Config['accordion'] is an AccordionConfig resolving to the {i18n: AccordionTranslations, rememberExpanded: boolean} type.

For earlier versions, AccordionConfig will resolve to any if I followed correctly what was happening before the @import tags being kept in the built output.

	With `@import` support	Without `@import` support
Completion
Resolution of `AccordionConfig`

This shouldn't break existing builds, just loosen the type checking a little (again, if I understand correctly). Will have a check with the team, but it doesn't feel like a blocker to start using @import.

[colinrotherham]

Think you're all set

IDEs and editors will discover @types/govuk-frontend now and this repo uses TypeScript 5.5+ already

Thanks @romaricpascal

[romaricpascal]

I've rebased the PR on main and it looks good to me. It'll need a second approval before we can merge it though.