🐛 Duplicate export on exported const variable equal to exported function

[JoshuaKGoldberg]

Prerequisites

• I'm using the latest version
• I've read the relevant documentation
• I've searched for existing issues
• I've checked the list of known issues
• I've read the issue reproduction guide

Reproduction url

https://github.com/JoshuaKGoldberg/ts-api-utils/tree/150b52ca67b79c403c5bd8acf2d3ba92a49765ee

Reproduction access

• I've made sure the reproduction is publicly accessible

Description of the issue

I have a few code pairs like this:

export function intersectionConstituents() {
  // ...
}

/** @deprecated use {@link intersectionConstituents}. */
export const intersectionTypeParts = intersectionConstituents;

Knip is reporting on those pairs:

Duplicate exports (3)
intersectionConstituents, intersectio...  src/types/utilities.ts
typeConstituents, typeParts               src/types/utilities.ts
unionConstituents, unionTypeParts         src/types/utilities.ts

I tried making a standalone reproduction but the bug didn't reproduce ☹. So I don't know what's specifically happening differently in ts-api-utils. But it's happening in JoshuaKGoldberg/ts-api-utils#713 on the latest knip@5.46.0.

[webpro]

This looks like expected behavior. Duplicate exports indicate the same thing/symbol being exported.

Am I right thinking you're asking for Knip to not report duplicates if one of them is tagged @deprecated?

You can already use @alias for that too!

[JoshuaKGoldberg]

Ah! TIL, I missed that note in the docs. Thanks!

not report duplicates if one of them is tagged @deprecated

Yes, that was my thought - but I can see why you would want to make sure @alias is there. I wouldn't be offended at all if you close this out. Or maybe the user request is explicitly mentioning @alias in the reporting for const variables like this?

[webpro]

Cool! Then I'm going to close this one as I feel this can be worked with.