Katsuyuki Omuro
Katsuyuki Omuro
Thanks for reaching out. we'll take a look at this.
Currently this is not a priority item on our roadmap, but if someone would be willing to contribute a PR we would be more than willing to look at it.
Thanks for the feedback, we're taking a look at this
Hi, thanks for the discussion and pull request. Will be taking a look at this soon, expect a release by next week.
This has been released in 6.1.1.
I may be missing something here, but in the same way that lookup returns KVStoreEntry which gives access to `metadata` (extending the `Body` interface), it seems to me that KVStoreEntry...
Something to note is that if I instead use a reader like this, I get the right result (so I'm currently using this as a workaround): ```javascript const text =...
Thanks for reaching out, we'll be taking a look.
Hi, can I have you examine the log output near ``` Exception while evaluating JS: (new Error("Automatic publicPath is not supported in this browser", "", 2)) @:2:16345416 @:2:16345558 @:2:16345971 ```...
The message "Automatic publicPath is not supported in this browser" indicates that your code, or a library you are including, triggers the [Automatic Public Path](https://webpack.js.org/guides/public-path/) feature of Webpack. This may...