It looks like deno makes requests with a user agent of "reqwest/...", which seems to be the default coming from that Rust package.
Maybe we need a standard compliant and Deno identified user agent when we import and run deno fetch with a url.
+1, as mentioned in that issue we're able to detect reqwest/* in the user-agent for now, but it would be nice to get a more deno-specific user-agent so that we can more reliably serve Deno-specific transpilation/polyfills from the Pika CDN.
@FredKSchott awesome that folks are considering throwing some Pika CDN magic towards Deno!
(also, agree that we should provide a UA string... I suspect this is an easy fix though). Feels like it should be a simple Deno/{version})
(also, agree that we should provide a UA string... I suspect this is an easy fix though).
Indeed it is.
Feels like it should be a simple
Deno/{version})
Agree, I'll add it later today :+1:
Thanks y'all! I'll update the CDN check for both "reqwest/*" & "Deno/*".
Looking forward to adding more Deno specific features to the Pika CDN in the coming months, but if you all have any ideas/requests feel free to shoot me a message / lmk! Better type def support via @deno-types is coming soon
Most helpful comment
Thanks y'all! I'll update the CDN check for both
"reqwest/*"&"Deno/*".Looking forward to adding more Deno specific features to the Pika CDN in the coming months, but if you all have any ideas/requests feel free to shoot me a message / lmk! Better type def support via
@deno-typesis coming soon