Bump debug, docpad and docpad-plugin-babel

[dependabot]

Bumps debug to 4.3.4 and updates ancestor dependencies debug, docpad and docpad-plugin-babel. These dependencies need to be updated together.

Updates debug from 2.2.0 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

• Add section about configuring JS console to show debug messages by @​gitname in debug-js/debug#866
• Replace deprecated String.prototype.substr() by @​CommanderRoot in debug-js/debug#876

New Contributors

• @​gitname made their first contribution in debug-js/debug#866
• @​CommanderRoot made their first contribution in debug-js/debug#876

Full Changelog: debug-js/debug@4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

• Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.
• Updates repository maintainership information
• Updates the copyright (no license terms change has been made)
• Removes accidental epizeuxis (#828)
• Adds README section regarding usage in child procs (#850)

Thank you to @​taylor1791 and @​kristofkalocsai for their contributions.

---

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@​qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits

• da66c86 4.3.4
• 9b33412 replace deprecated String.prototype.substr() (#876)
• c0805cc add section about configuring JS console to show debug messages (#866)
• 043d3cd 4.3.3
• 4079aae update license and more maintainership information
• 19b36c0 update repository location + maintainership information
• f851b00 adds README section regarding usage in child procs (#850)
• d177f2b Remove accidental epizeuxis
• e47f96d 4.3.2
• 1e9d38c cache enabled status per-logger (#799)
• Additional commits viewable in compare view

Maintainer changes

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

Updates docpad from 6.79.4 to 6.83.2

Changelog

Sourced from docpad's changelog.

v6.83.2 2020 September 8

• If the source path is missing, the correct and useful error is now displayed
• The deprecated srcPath is now removed, use sourcePaths to write and getPath('source') and getPath('sources') to read
• Extra debugging for when getting a path fails
• Updated documentation and website links to their new locations

v6.83.1 2020 August 5

• Add a new loadPlugins event for use in the docpad-plugintester to make sure all test plugins are properly loaded before docpadReady and other events are fired

v6.83.0 2020 August 5

• Removed superflous option aliases
  • outPath => outpath
  • configPaths, configPath, c => config
  • environment, e => env
  • logLevel => log
  • render --out, render -o => render --output
• Removed offline option, it can be re-added later if anyone uses it
• Removed the last bits of docpad cloud helper functionality
  • Removed skeleton functionality, just clone the repo from github instead
    • docpad skeleton => docpad init (same functionality as selecting no sekleton)
  • Removed version check
• Updated dependencies, base files, and editions using boundation
  • This will bring a massive performance boost to DocPad, especially with Caterpillar v6 which allows DocPad to disable fetching line information (a very expensive process) for log messages we don't care about
• Minimum required node version changed from node: >=6 to node: >=10 to keep up with mandatory ecosystem changes

v6.82.5 2018 October 1

• Prevent plugin false could not be loaded errors, now it will output the path that failed to be found, as expected

v6.82.4 2018 September 8

• Report the correct error for missing action requests
• Ensure docpad-plugintester dependency is latest

v6.82.3 2018 September 8

• Swapped out promptly for inquirer, which brings back Node v6 support (regression since v6.82.1)
  • Close [issue #1093](docpad/docpad#1093)

v6.82.2 2018 September 8

• Add logging support to the pluginloader to make debugging plugin resolutions easier
• Fixed failures of plugin loading and creation not being reported correctly
• Ensure all dependencies are the latest right now, to help fix false negatives in plugin resolution
• Close [thread #248](https://discuss.bevry.me/t/plugins-broken-in-6-82-1/573?u=balupton)

v6.82.1 2018 September 7

... (truncated)

Commits

• 85b3297 v6.83.2 - bugfixes
• e36e387 Bump underscore from 1.10.2 to 1.11.0 (#1119)
• e44cac1 Bump watchr from 6.6.0 to 6.8.0 (#1118)
• a7fe51a Bump scandirectory from 6.11.0 to 6.13.0 (#1116)
• 81929c3 Bump safefs from 6.11.0 to 6.12.0 (#1113)
• 0e9c4e0 Bump rfc-log-levels from 3.12.0 to 3.13.0 (#1114)
• 080eed2 Bump cson from 7.18.0 to 7.19.0 (#1112)
• 5d8cc07 Bump valid-directory from 3.0.0 to 3.2.0 (#1111)
• a8f1f12 Bump kava from 5.10.0 to 5.11.0 (#1110)
• f14ffee Bump ignorefs from 3.11.0 to 3.12.0 (#1109)
• Additional commits viewable in compare view

Updates docpad-plugin-babel from 2.2.1 to 2.5.0

Changelog

Sourced from docpad-plugin-babel's changelog.

v2.5.0 2020 October 29

• Updated dependencies, base files, and editions using boundation

v2.4.0 2020 September 8

• Updated dependencies, base files, and editions using boundation

v2.3.0 2020 August 5

• Updated dependencies, base files, and editions using boundation
• Minimum required node version changed from node: >=0.8 to node: >=10 to keep up with mandatory ecosystem changes

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by bevryme, a new releaser for docpad-plugin-babel since your current version.

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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.