feat: support passing envFilePath to NodeKit constructor#117
Merged
Conversation
yainsulin
changed the title
yainsulin
force-pushed
the
ISSUE-116/support-dotenv-config-options
branch
2 times, most recently
from
27dc421 to
0d7b02e
Compare
yainsulin
force-pushed
the
ISSUE-116/support-dotenv-config-options
branch
from
0d7b02e to
56db9ee
Compare
resure
approved these changes
Mar 26, 2026
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.
Summary
envFilePathfield toInitOptionsfor specifying a custom.envfile pathdotenv.config({path}), keeping the API minimal and migration-friendlyprocess.loadEnvFile(path)becomes the target, the public API stays the sameCloses #116
Test plan
envFilePathforwarding addedenvFilePathis not provideddisableDotEnvstill works