Blake Embrey

If you look in the test snapshots, you can find some microdata instances exposing product and other information. The snippet process is two step - first step is extraction of...

It was refactored away into Jest snapshots. Same thing, different format basically.

Two thoughts: 1. Let's improve https://github.com/blakeembrey/node-scrappy/blob/d63aaa5613901594730105a895efb397597d0d6d/src/extract/helpers/icon-selector.ts#L32-L33 so it uses itself (instead of using the default configurations), that way you can disable https://github.com/blakeembrey/node-scrappy/blob/d63aaa5613901594730105a895efb397597d0d6d/src/scrape/plugins/exif-data.ts which is your issue (this is used for...

1. Happy to publish, haven't really been working on this much though 2. Would love to accept PRs with more examples

https://schema.org/potentialAction

I've honestly thought a lot about it and couldn't think of any way to reconcile all the different formats into a better standardisation. Currently I'm parsing as many as possible...

One example is that the extracted result (not the direct parse result) could be a manual combination of the different results into a standard vocabulary like JSON-LD. That's the primary...

Oh, but if you have ideas, let me know! I'm definitely very interested in being able to squash the snippets down into a standard object instead of defining a bunch...

So I did give this some more thought. It'd be great to move everything to using some sort of vocabulary and JSON-LD. What that looks like still seems quite messy...

I did a bit (lots) more refactoring of how this module parses and generates metadata/snippets internally and released it as `0.3`. The model is hopefully a bit simpler and getting...