Usage as a library

[P4]

Hi, I've been using @biesbjerg/ngx-translate-extract in my project at work for several years now. However, we needed to make enough changes to the resulting files that we ended up writing our own custom script that's using the parsers and collections provided by the package, essentially treating the tool as a library.

We're currently using @biesbjerg/ngx-translate-extract version 7.0.4

A small problem we have right now is that any attempt to import something from the package's main entrypoint causes the CLI task to execute and kill the process. I suspect this is caused by the index.ts file re-exporting another file which defines and executes the task:

ngx-translate-extract/src/index.ts

Line 4 in 82eb652

export * from './cli/cli';

ngx-translate-extract/src/cli/cli.ts

Lines 152 to 158 in 82eb652

	// Run task
	try {
	extractTask.execute();
	console.log(green('\nDone.\n'));
	console.log(donateMessage);
	process.exit(0);
	} catch (e) {

We currently work around that by importing everything from internals instead of the main entrypoint:

import {JsonCompiler} from '@biesbjerg/ngx-translate-extract/dist/compilers/json.compiler';
import {ParserInterface} from '@biesbjerg/ngx-translate-extract/dist/parsers/parser.interface';
import {PipeParser} from '@biesbjerg/ngx-translate-extract/dist/parsers/pipe.parser';
...

This works, but looks messy is generally not a good practice, so I was wondering if there's any good way to solve that issue. I'm not certain why cli is re-exported as it does not seem to be used through index, and the bin script that actually runs as ngx-translate-extract imports it directly.

Thanks!