Select which adblock data files to generate using cli args

[tontinton]

No description provided.

[antonok-edm]

@tontinton thanks for submitting this!

Unfortunately there are a few dependencies between components that are left in for historical reasons, e.g. the regional data files depend on the default component files here.

I'm hoping to get rid of those dependencies eventually, but I don't want to suddenly break things for older browser versions that haven't updated in a while. In the meantime we still have to do most^† of these in order.

So, I can't merge this just yet, but hopefully I can get to it in the future.

^{† I say "most" because the test data files can definitely be generated in parallel... but those can probably be removed altogether, too. I don't believe we have any code that would be using them anymore (#701).}

[tontinton]

Ok I updated the PR to only include the cli stuff, will be useful for me (I want to generate only the default list)

[tontinton]

bumping, still keeping a fork :(

regional lists sometimes return 404, while the default seems to work all the time.

[tontinton]

another final bump? 😅

[antonok-edm]

@tontinton sorry for the delay, but the reorganization in #844 should make this significantly easier. All the components will be "self-contained", i.e. not dependent on other component jobs running.

Going forward:

• once merged you could immediately patch getAdblockComponentDescriptors to skip the components you're not interested in
• later, I'm planning to move the per-component classes to exports in their own files; making the packaging scripts themselves basically just these lines. Then you can treat this repo as a library dependency and define a custom entrypoint to drive the logic of which components to package.