Is it possible to reuse the logic of dependency tree crawling?

[yunsii]

Problem Description

We also want to extract something by dependency tree crawling. For example, get all special classnames with regexp matching. Is it possible to be supported?

Proposed Solution

Provide a extra callback in experimental.extractor?

Alternatives Considered

Re-implement dependency tree crawling by ourselves.

Additional Context

No response

[timofei-iatsenko]

Dependency tree crawling is basically done by the esbuild. It creates a single bundle which then processed by the basic lingui extractor.

You can write your own extractor implementation and pass it to the lingui config. This implementation might do whatever you need with class names and then call original implementation. This way you will have this "extra callback". Your implementation would be called for the whole bundle created by esbuild, not for the individual files.

If you want to call something for the individual files processed by the tree extractor, you might need to write a esbuild plugin and pass it to the experimental.extractor.resolveEsbuildOptions you can check a macro plugin implementation for the inspiration

[yunsii]

If you want to call something for the individual files processed by the tree extractor, you might need to write a esbuild plugin and pass it to the experimental.extractor.resolveEsbuildOptions you can check a macro plugin implementation for the inspiration

Thanks for your detailed explaination. This is the way I was expecting.