You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An app that imports fsthttp, and which builds in both go, tinygo native, and tinygo wasm
(with -tag nofastlyhostcalls) stopped building on tinygo native when we upgraded it to
v0.1.2; wrapping fsthttp/{transport,adapter}.go in another build tag seems to resolve the problem.
So adding a build tag to disable the net/http dependency seems like a good thing to add...
maybe named fastly.compute.nostdhttp for clarity.
The text was updated successfully, but these errors were encountered:
This seems reasonable. The net/http package is also a large dependency, and people who are only using C@E won't need it. That's probably easier than moving those two files to their own subpackage.
I wonder if we should actually go the other way and require opting in to the net/http dependency? Although if we're going to break the API, having it in a separate package is probably nicer.
An app that imports fsthttp, and which builds in both go, tinygo native, and tinygo wasm
(with -tag nofastlyhostcalls) stopped building on tinygo native when we upgraded it to
v0.1.2; wrapping fsthttp/{transport,adapter}.go in another build tag seems to resolve the problem.
So adding a build tag to disable the net/http dependency seems like a good thing to add...
maybe named fastly.compute.nostdhttp for clarity.
The text was updated successfully, but these errors were encountered: