[Recommendation] Separate the HTML parser framework from the core library

[pavlovtech]

[Recommendation] Separate the HTML parser framework from the core library

[pavlovtech]

@iyilm4z thank you, appreciate the feedback! Creating a separate project for 3rd party dependencies indeed makes sense. However, any referenced projects must be published as separate NuGet packages as well, which is not practical if your package is not going to work without it and it would be installed anyways.

For the most part, 3rd party dependencies in Exoscan are abstracted away via interfaces, so it is possible to swap out the implementation, e.g. IBrowserPageLoader with PuppeteerPageLoader implementation.

I'm planning to move some optional external dependencies to separate packages such as Redis, Mongo DB, Azure Service Bus, etc.

But I see that I have a tight coupling with HtmlAgilityPack and creating Exoscan.AngleSharp makes sense as well, thank you for pointing that out!

[iyilm4z]

Also the same for Puppeteer. I prefer Playwright.