Mot

I haven't been able to solve these issues yet, given VSCode limitations. I'm still looking.

if you install [`dotenvx`](https://github.com/dotenvx/dotenvx) does that fix your issue? ``` npm install @dotenvx/dotenvx --save ``` ``` { "name": "vercel", "version": "0.0.1", "private": true, "scripts": { "dev": "dotenvx run --verbose --...

Process started here: https://github.com/EclipseFdn/open-vsx.org/issues/1250 Notes: https://github.com/eclipse/openvsx/wiki/Namespace-Access#how-to-claim-a-namespace

Additional notes: https://coder.com/docs/code-server/latest/FAQ#how-do-i-install-an-extension https://github.com/orgs/dotenv-org/discussions/95#discussioncomment-3706987

Thanks for this gcullins. I'll look at this as soon as I can.

i'll look into this and we might go back on that new default. or might provide a different solution. thank you for raising this.

@jahdiel what version did you bump up from? And does your `HOST` value have a `$` dollar sign in it?

@jahdiel nevermind. i see the issue. working on the fix. so sorry about this. in the meantime, you can fix it by changing your dotenv expand code from: ```js var...

@jahdiel - please install `v11.0.3`. should be fixed. https://github.com/motdotla/dotenv-expand/pull/113 sorry about this one. was a bad one. tests were formatted badly allowing it to sneak in. fixed going forward.

TLDR: This is great to see from Node, but we don't recommend dropping dotenv just yet. The Node native feature is [missing some key features at the moment](https://www.dotenv.org/blog/2023/10/28/node-20-6-0-includes-built-in-support-for-env-files.html). --- ##...