The LoaderRegistry used to resolve format-specific loaders once the remote content type is known.
Fetch source over HTTP/HTTPS and return a LoadedDocument.
The response body is buffered in memory and then handed to the appropriate
sub-loader according to the Content-Type header:
text/html → fetched as text, passed to the HTML loader as a Buffer.application/pdf → fetched as bytes, passed to the PDF loader as a
Buffer.'text' and
source metadata set to the URL.HTTP/HTTPS URL string.
Optional options: LoadOptionsOptional load hints forwarded to the delegated loader.
A promise resolving to the LoadedDocument.
When source is a Buffer (URLs must be strings).
When the HTTP request fails (network error or non-2xx status).
Readonly supportedURLs have no file extension so this array is always empty.
Routing to this loader must be performed via canLoad rather than the registry's extension-based lookup.
An IDocumentLoader that fetches a remote URL and delegates parsing to the appropriate registered loader based on the response
Content-Type.Supported content types
text/htmlapplication/pdfExample
Implements