Environment variables are exposed to public about deno-playground HOT 3 CLOSED

Holyshit

yep that's true, and I didn't think thoroughly before - and it seems that there are some vercel-specific AWS credentials on the envvars.

this is due to the now-deno runtime that this project uses: https://github.com/lucacasonato/now-deno/blob/master/src/index.ts#L26

which in turn uses deno-lambda, which specifies -A flags to deno: https://github.com/hayd/deno-lambda/blob/2c5ef7062a04078996387fae62772331bf6cf665/runtime/bootstrap#L22

I'm not sure how to fixes this - I think it's better to contact vercel first, lemme do that.

Thanks for the findings!

from deno-playground.

Also I merged a temporary fixes, very basic and naive solutions to deno playground which disables Deno.env execution

from deno-playground.

I'll lock the conversation for now, while waiting vercel support to reply

from deno-playground.