arethetypeswrong / arethetypeswrong.github.io

Tool for analyzing TypeScript types of npm packages

Home Page:https://arethetypeswrong.github.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Can I ignore an entry in exports?

NullVoxPopuli opened this issue · comments

my packages have a legacy/support entrypoint, which isn't exactly public API, but is there for folks who know about.

It's also a CJS module, but with an ambiguous entry in the exports.
I'd like to ignore checking this file / exports, because it ultimately wouldn't be used by 99.999% of users.

Is this possible? possible soon? thanks!!

Yes 😄

I also have a similar scenario, but for .css files that my component library exposes.

Does it make sense to exclude them? Or would it be better to provide a .d.ts for those .css files?

It probably makes more sense to exclude them.

How can we exclude CSS files then?

@RobbieTheWagner Looks like this'd be done over with the CLI's --exclude-entrypoints argument, which can also be pre-specified in the .attw.json file.