[demo-shop] Update dotenv 16.0.3 → 16.3.1 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ dotenv (16.0.3 → 16.3.1) · Repo · Changelog

Release Notes

16.3.1 (from changelog)

Added

• Add missing type definitions for processEnv and DOTENV_KEY options. #756

16.3.0 (from changelog)

Added

• Optionally pass DOTENV_KEY to options rather than relying on process.env.DOTENV_KEY. Defaults to process.env.DOTENV_KEY #754

16.2.0 (from changelog)

Added

• Optionally write to your own target object rather than process.env. Defaults to process.env. #753
• Add import type URL to types file #751

16.1.4 (from changelog)

Added

• Added .github/ to .npmignore #747

16.1.3 (from changelog)

Removed

• Removed browser keys for path, os, and crypto in package.json. These were set to false incorrectly as of 16.1. Instead, if using dotenv on the front-end make sure to include polyfills for path, os, and crypto. node-polyfill-webpack-plugin provides these.

16.1.2 (from changelog)

Changed

• Exposed private function _configDotenv as configDotenv. #744

16.1.1 (from changelog)

Added

• Added type definition for decrypt function

Changed

• Fixed {crypto: false} in packageJson.browser

16.1.0 (from changelog)

Added

• Add populate convenience method #733
• Accept URL as path option #720
• Add dotenv to npm fund command
• Spanish language README #698
• Add .env.vault support. 🎉 (#730)

ℹ️ .env.vault extends the .env file format standard with a localized encrypted vault file. Package it securely with your production code deploys. It's cloud agnostic so that you can deploy your secrets anywhere – without risky third-party integrations. read more

Changed

• Fixed "cannot resolve 'fs'" error on tools like Replit #693

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)