allow for import "dotenv/config.js" #534
Merged
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.
Adding
dotenv/config
as a named export in 8.5.0 had the side effect ofdotenv/config.js
no longer being recognised as an import path.For example, after upgrading to 9.0.0, I got the following error:
Some linters enforce using file extensions in imports, i.e. eslint-plugin-import and eslint-plugin-node.
Explicitly adding
dotenv/config.js
ensures projects following this style can continue to use the.js
extension when importingdotenv
.