fix: suppress dotenv startup banner by default - #155
Open
resure wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Pass
quiet: truewhen NodeKit initializes dotenv so its default startup banner and promotional tips no longer appear in application logs. Apply the option for both the default.envfile and customenvFilePathvalues, while preservingdisableDotEnvbehavior and dotenv's environment-controlled overrides.Update the existing integration tests to assert quiet loading for both paths.
Validation:
npm test(15 suites, 118 tests),npm run lint, andnpm run typecheckpass on Node.js 24.12.0.Complete dependency removal and a Node.js support update are tracked separately in #154 for the next major.