Spurious fail caused by `fetch("https://some.url.that/only/accepts/post", { method: "POST" })` about hyperlink HOT 2 CLOSED

Fetch had always been difficult to reason about for assetgraph. There's are cases where it's used to fetch internal static assets, which would make sense to check, and in assetgraphs other user cases to include in the build. But this case is obviously wrong behavior, and hyperlink also shouldn't attempt other http methods either.

I'm inclined to say that hyperlink should maybe just assume fetch is not used for static content by default, and not check the link at all.

It maybe it should only follow fetch requests if the URL had a known static file extension.

@papandreou what do you think?

from hyperlink.

I think we should stop modelling fetch And let users opt in with fetch(‘/foo.json’.toString(‘url’)).

from hyperlink.