Initial release#1
Merged
Merged
Conversation
…hould-log-env configuration value
…or more idiomatic getPropertyValue() usage
… be disabled with via config 'should-log-env', tweaked some of the stdout formatting
Also removed some old sample .env files
…b/dependabot.yml to auto-bump prod dependencies Also cleaned up .gitignore - there were a bunch of files being ignored that currently won't be in this repo, so I've simplified it
…v file + controlling if (potentially sensitive) env variable values are printed out This also includes updating code to consistently use the ux import for logging, and making loadingMessage.ts to centralize printing out env vars so everything is consistent for dotenv command and prerun hook This also ALSO includes adding in new test files for dotenv.ts command and some of the shared helper files
…he plugin on npmjs.org
…st tests within VS Code I typically don't commit anything in .vscode, but I want to make sure I can easily run tests via an extension, without having to reconfigure this on different machines
…onally) overridden if they're defined in the specified .env file
…eviously worked locally but not in GitHub Actions)
… issues with the shouldLog value being used for the hook version of the plugin, and updated the tests accordingly. Suppressed a few ts-jest warnings that are only applicable to tests and don't affect how the production-level plugin actually works, which were polluting the console on subsequent test runs
…grading to TypeScript 6.0 (https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/#deprecated:---baseurl) - ESLint hasn't been updated to support the new version of TypeScript yet, so we have to wait for upstream support there prior to completely porting over
…st directory structure to match the src directory structure
…ncorrectly) passed as the value for --output-file
…ing *.test.ts file)
…t are used as replacements in sfdx-project.json
… to ensure one-liners still are wrapped in {} curly braces
jamessimone
reviewed
Mar 24, 2026
jamessimone
reviewed
Mar 24, 2026
- Added some scripts to generate oclif.manifest.json at packaging time so installs skip runtime command discovery (`prepack` now runs `oclif manifest`; `postpack` cleanup of the file already existed). Adds `oclif` to devDependencies and gitignores the generated artifact. - Removed unused `messages/**/*` and `npm-shrinkwrap.json` from the `files` array in package.json - Added a .prettierignore file to skip lib/, coverage/, oclif.manifest.json, and some IDE-only directories - Started ignoring `coverage/**` in eslint.config.js j- there's no need to run lint here, and the files in there cause lint warnings on generated coverage HTML - Remove Contributing.md / CODE_OF_CONDUCT.md from build.yml's paths-ignore (those files do not exist) and add .prettierignore to the list
- `README.md`: updated content to rename `sf dotenv` to `sf dotenv inspect` and document the new `sf dotenv export` command - `publish.yml`: bump Node 18 -> 20 to match engines and build.yml - Also added `id-token: write` permission for `npm publish`, - And also added a step that fails the job if the pushed tag doesn't match the version number in `package.json`
… (based on some PR feedback from @jamessimone)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the first release of a new
sfCLI plugin for loading.envfiles when using anysfCLI commandHighlights of features:
.envfile (default:.envin the current directory) before everysfcommand. Values from the file override existing env vars of the same name; others are left unchanged.--env/-ewith any command to load a specific file (e.g.sf project deploy start --env .env.prod).sf config set should-log-env falsedisables prerun logging of variable names. Optional env vars:SF_DOTENV_DISABLED,SF_DOTENV_FILE.dotenvcommands:sf dotenv inspect- Loads a given.envfile and prints the loaded variable names; pass--show-valuesto also print values (with a security warning).sf dotenv export- ReadsreplaceWithEnventries fromsfdx-project.jsonand writes any missing keys to a.envfile, defaulting any value already present in the shell's environment. Use--output-file/-oto target a non-default file.