dotenv-vscode
dotenv-vscode copied to clipboard
dotenv-org
Add auto-cloaking, auto-completion, in-code secret peeking, and more to VSCode.
When I just want to look at the environment variables in my `.env` file and want to `Toggle auto-cloaking` to `off`, I click and none of my environment variables are...
This happens on my other devices, I don't know if I'm missing something (my NodeJs project currently doesn't have dotenv package installed) file .env  file index (even after restart...
I have a file called `.env.local` with some variables inside. In a TypeScript file when I type `process.env.` the variables from the `.env.local` file don't show up. Would that be...
Instead of associating a list of file extensions starting with `.env` with the `dotenv` language, The `dotenv` language is now associated with the `.env*` filename pattern. This also removes the...
I have a `.vscode/settings.json` in my workspace: ```json // (workspace) .vscode/settings.json { "files.associations": { "*.css": "postcss", }, } ``` but In my user `settings.json`, I didn't set the file associations:...
Not sure if something broke with my configuration, but this ruins the point of a cloaking feature, and I would recommend removing it if it can't be solved as it...
This would be a great addition. Currently only https://github.com/IronGeek/vscode-env supports it.
Allow using a setting similar to the one below to associate a custom file as a `dotenv` file: ```json { "dotenv.files.associations": { "**/.env.d/*": "dotenv", }, } ```
`dotenv pull` pulls an unencrypted `.env` file to the local file system. While this file could be git-ignored, it would still contain secrets in plaintext sitting on the file system....
Hey, It looks like your extension is adding some garbage to my config. Please stop this. Reloading with zero extensions:  Enabling this extension: 
Metadata
Owner
Metadata
Add auto-cloaking, auto-completion, in-code secret peeking, and more to VSCode.