IDEA: Convert indexer script into CLI package

[ArrayKnight]

It would be nice to be able to use the indexer script in a slightly more generic manner which is targeted at JS/TS export collating.

My desired features:

• Accept a config file (CLI flags remain an option)
• Accept output file path
• Accept an include glob / glob array for target files to import into output file
• Input target files are relative to output file
• Accept banner (in place of hardcoded header, but current value can be default)
• Accept exclude glob / glob array. Yes, glob negation in includes would work. But this option is more targeted something that might be external or as a shared set of exclude between multiple configs
• Add in a deduping function that renders // __private-exports unnecessary

Examples:

O: src/index.ts I: **/*.{ts,tsx}
O: src/index.ts I: **/index.{ts,tsx} (similar to current --barrel flag)
O: src/components/index.ts I: */index.ts
O: src/vanilla.ts I: **/*.css.ts, **/types.ts, ./types/*.ts, ./styles/*.ts, ./utils/css.ts
exclude: ['**/*.{spec,stories,test}.*']

[ArrayKnight]

Thanks, @belsrc

Clarity on the scope of deduping:

• Potentially do the parsing in a depth first approach, and track the origin of an export, then you might be able to safely ignore imports later in the parsing cycle
• Deduping can absolutely be a future feature. We could get the initial effort launched and then see if that can be added later
• If a.ts and b.ts both export type Foo, but they are unique, then that's an error that the user has to deal with
• If a.ts exports type Foo and b.ts reexports everything from a.ts, then everything that is a dupe export in b.ts can be safely skipped

[ArrayKnight]

We also talked about having an option in the config that allows for a custom formatter (Biome, Prettier, etc) to be run against the file contents before write

[belsrc]

Thinking about that....I think we could probably just handle it like the extensions. postprocessing or something. Leave it for the user to decide. At that point, it would just be receiving essentially a js/ts file body content which is what most expect when they are used from inside code?

[belsrc]

Unless you have a different opinion, I'm just going to self assign this @ArrayKnight