Bump lodash and aurelia-webpack-plugin in /src/NSwag.Sample.NetCoreAurelia

[dependabot]

Bumps lodash to 4.17.21 and updates ancestor dependency aurelia-webpack-plugin. These dependencies need to be updated together.

Updates lodash from 4.17.4 to 4.17.21

Commits

• f299b52 Bump to v4.17.21
• c4847eb Improve performance of toNumber, trim and trimEnd on large input strings
• 3469357 Prevent command injection through _.template's variable option
• ded9bc6 Bump to v4.17.20.
• 63150ef Documentation fixes.
• 00f0f62 test.js: Remove trailing comma.
• 846e434 Temporarily use a custom fork of lodash-cli.
• 5d046f3 Re-enable Travis tests on 4.17 branch.
• aa816b3 Remove /npm-package.
• d7fbc52 Bump to v4.17.19
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by bnjmnt4n, a new releaser for lodash since your current version.

Updates aurelia-webpack-plugin from 1.2.2 to 5.0.6

Release notes

Sourced from aurelia-webpack-plugin's releases.

5.0.4

What's Changed

• Register dependency serializers by @​elitastic in aurelia/webpack-plugin#205
• Fix serialization for component modules when imported via the normal way in aurelia/webpack-plugin#205

New Contributors

• @​elitastic made their first contribution in aurelia/webpack-plugin#205

Full Changelog: aurelia/webpack-plugin@v5.0.3...5.0.4

5.0.3

The plugin now works with webpack v5, all deprecation warnings also have been resolved to prepare for any future major changes from webpack. Typings are also added so that it's easier to get intellisense for all the options/features the plugin has to offer. Added tests to prevent unwanted breakage with different webpack plugins/ aurelia packages.

4.0.0

Removed the runtime insertion hack from the Webpack 3 and below era, wherein only the first "entry" item had the runtime appended to it. This was originally implemented to avoid adding the runtime to the secondary "vendor" entry. Using "vendor" entry points which is no longer recommended for Webpack 4 and up.

3.0.0

Upgrade the RC to release.

3.0.0-rc.1

aurelia-webpack-plugin 3.0.0-rc.1

We've updated our Webpack plugin to support Webpack 4.0! Please note that because of breaking changes in Webpack's plugin model, we cannot support Webpack 2.0/3.0 with this plugin. If you cannot migrate to Webpack 4.0, then you will need to continue using aurelia-webpack-plugin 2.0.0-rc.5.

2.0.0-rc.5

fix(webpack): ConcatenatedModulePlugin results in an exception.

2.0.0-rc.4

• fix(at-loader): Incompatibility with awesome-typescript-loader

2.0.0-rc.3

aurelia-webpack-plugin 2.0.0-rc.3

Features

• support Webpack 3 ModuleConcatenationPlugin
• support resources inside @​inlineView

Bug Fixes

• recognize router-view attributes
• better control over entry sequence
• chunk not supported by ModuleDependenciesPlugin
• no default entrypoint with DLLPlugin
• use browser-pal for electron-renderer (#100)

2.0.0-rc.2

aurelia-webpack-plugin 2.0.0-rc.2

... (truncated)

Changelog

Sourced from aurelia-webpack-plugin's changelog.

5.0.4

Fix webpack serialization when a component module is imported via the normal way

5.0.3

Fix webpack v5.52.0 error with mini-css-extract-plugin

4.0.0

Remove the runtime insertion hack from the Webpack 3 and below era, wherein only the first "entry" item had the runtime appended to it. This was originally implemented to avoid adding the runtime to the secondary "vendor" entry. Using "vendor" entry points which is no longer recommended for Webpack 4 and up.

3.0.0

• Promote the RC to release.

3.0.0-rc.1

Supports only Webpack 4.x

2.0.0-rc.3

Features

• support Webpack 3 ModuleConcatenationPlugin
• support resources inside @​inlineView

Bug Fixes

• recognize router-view attributes
• better control over entry sequence
• chunk not supported by ModuleDependenciesPlugin
• no default entrypoint with DLLPlugin
• use browser-pal for electron-renderer (#100)

2.0.0-rc.2

Features

• flag to opt-out of IE support
• support module.loaders

Bug Fixes

• errors might crash SubFolderPlugin
• compat with IE < 11
• support more CommonJS import styles

2.0.0-rc.1

... (truncated)

Commits

• dbcf73c chore(release): prepare release 5.0.6
• 492e434 fix: broken webpack mangling of harmony imports in production mode (#223)
• 663b24d chore(deps): bump dns-packet from 5.3.1 to 5.4.0 (#217)
• 12c8351 chore: prepare release 5.0.5
• a10d632 fix(dep): use internal copy of bundle-loader (#216)
• c1cc84b chore: upgrade deps (#208)
• 4d486c9 chore(release): prepare release 5.0.4
• 6a08665 fix(serialization): patch webpack serialization to handle [preserveModuleName]
• c41ce6c chore: add karma test for file cache
• 5657c74 fix: pnpm test ci config
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.