Brian LeRoux

@jlipps yes, unfortunately for me too. works on arm tho

This is a great idea. While today Node is already an indispensable tool for web developers it does not enjoy the same full seat at the table of web browser...

I'd love to support this! I also don't know the first thing about writing a declaration file 😬 any tips to get started and/or would you like to help out...

lets add a new method rather than overloading this one; how about `arc.static.manfiest` ?

thought about this for a while and I agree; this would be a better behavior… also a breaking change I think so I'll poll other maintainer opinions here. thx for...

IMO this is security theatre. There are two audiences for runtimes security. People running workloads on the cloud. And people running local dev tools on their machine. With the cloud...

fwiw many versions of the sdk shouldn't be an issue; aws only adds stuff they don't remove stuff. no idea how the new sdk is going to screw w this...

FYI for folks reading this… we currently do make the ws endpoint url available as an env var to all deployed lambdas in an Architect app `process.env.WSS_URL`

No, just would allow connection and message sending from a relative path so the socket endpoint doesn't need to live in env vars for discovery

(cookies work btw! It's a bit weird to setup but can walk you thru it)