Upgrade webpack-node-externals to version 3.0.0

[depfu]

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

What changed?

✳️ webpack-node-externals (1.7.2 → 3.0.0) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by 33 commits:

• 3.0.0
• change vars to consts
• add eslint
• better args handling
• upgrade test webpack, bump node version to 6
• 2.5.2
• remove deprecation notice trigger
• 2.5.1
• dont validate undefineds
• 2.5.0
• throw an error when using wrong spelling of an option
• support webpack 5
• 2.4.0
• add options validation
• 2.3.0
• Merge pull request #71 from brandon-leapyear/modulesFromFile
• Merge branch 'master' into modulesFromFile
• 2.2.0
• change parameter name (still supports the old one)
• Revert "Use modulesFromFile after it's already extracted"
• Update README.md
• 2.1.0
• support `additionalModuleDirs`
• Merge pull request #53 from Kizl/master
• 2.0.0
• Merge pull request #75 from mcous/refactor_replace-whitelist
• Merge pull request #74 from mcous/chore_upgrade-mock-fs-dep
• Replace "whitelist" option with "allowlist"
• Upgrade mock-fs dev dependency to support Node v12
• Add fileName docs
• Allow absolute path in fileName
• Use modulesFromFile after it's already extracted
• add 'additionalModuleDirs' to add to the list of node_modules directories to scan for modules

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

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 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)

Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.