Eric Burel @ericburel.tech · Feb 16

I need to setup a few more environment variables that are expected by underlying libs I've noticed some hard-written "process.env", they are problematic because Astro seems to use ESM where we use "import.meta.env" instead I need to use a global map instead

0 likes 1 replies

?

Replies

Eric Burel · Feb 16

It's indeed fixed by using our internal utility. Now I am hitting an error "Unexpected token < in JSON at position 0" This one trips up beginners, but as an experienced bug write, I know what it's all about: an API that should return JSON is instead returning HTML (an error or the wrong page)