fix(deps): update npm dependencies updates by renovate[bot] · Pull Request #116 · hackariens/expressjs

renovate · 2025-11-03T02:28:06Z

This PR contains the following updates:

Package	Change	Age	Confidence
cookie-parser	`1.4.5` → `1.4.7`
cypress (source)	`15.5.` → `15.15.`
debug	`4.3.1` → `4.4.3`
http-errors	`1.8.0` → `1.8.1`
jscpd	`4.0.` → `4.2.`
morgan	`1.10.0` → `1.10.1`
nodemon (source)	`2.0.7` → `2.0.22`
release-it	`19.0.` → `19.2.`

Release Notes

expressjs/cookie-parser (cookie-parser)

`v1.4.7`

Compare Source

==========

deps: cookie@0.7.2
- Fix object assignment of hasOwnProperty
deps: cookie@0.7.1
- Allow leading dot for domain
  - Although not permitted in the spec, some users expect this to work and user agents ignore the leading dot according to spec
- Add fast path for serialize without options, use obj.hasOwnProperty when parsing
deps: cookie@0.7.0
- perf: parse cookies ~10% faster
- fix: narrow the validation of cookies to match RFC6265
- fix: add main to package.json for rspack
deps: cookie@0.6.0
- Add partitioned option
deps: cookie@0.5.0
- Add priority option
- Fix expires option to reject invalid dates
- pref: improve default decode speed
- pref: remove slow string split in parse
deps: cookie@0.4.2
- pref: read value only when assigning in parse
- pref: remove unnecessary regexp in parse

`v1.4.6`

Compare Source

==================

deps: cookie@0.4.1

cypress-io/cypress (cypress)

debug-js/debug (debug)

`v4.4.3`

Compare Source

Functionally identical release to 4.4.1.

Version 4.4.2 is compromised. Please see #1005.

`v4.4.1`

Compare Source

What's Changed

fix(Issue-996): replace whitespaces in namespaces string with commas globally by @pdahal-cx in #997
fixes #987 fallback to localStorage.DEBUG if debug is not defined by @lzilioli in #988

New Contributors

@pdahal-cx made their first contribution in #997
@lzilioli made their first contribution in #988

Full Changelog: debug-js/debug@4.4.0...4.4.1

`v4.4.0`

Compare Source

Fixes (hopefully) the inefficient regex warnings in .enable().

Minor version as this is invariably going to break certain users who misuse the .enable() API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.

Full Changelog: debug-js/debug@4.3.7...4.4.0

`v4.3.7`

Compare Source

What's Changed

Upgrade ms to version 2.1.3 by @realityking in #819

Full Changelog: debug-js/debug@4.3.6...4.3.7

`v4.3.6`

Compare Source

What's Changed

Avoid using deprecated RegExp.$1 by @bluwy in #969

New Contributors

@bluwy made their first contribution in #969

Full Changelog: debug-js/debug@4.3.5...4.3.6

`v4.3.5`

Compare Source

Patch

cac39b1 Fix/debug depth (#926)

Thank you @calvintwr for the fix.

`v4.3.4`

Compare Source

What's Changed

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

New Contributors

@gitname made their first contribution in #866
@CommanderRoot made their first contribution in #876

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

`v4.3.3`

Compare Source

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.

I understand there are a lot of edge cases so please open issues as needed so I can assist in any way necessary.

Q: Why was the repository transferred?

I'll just list them off in no particular order.

The old organization was defunct and abandoned.
I was not an owner of the old organization and thus could not ban the non-trivial amount of spam users or the few truly abusive users from the org. This hindered my ability to properly maintain this package.
The debug ecosystem intends to grow beyond a single package, and since new packages could not be created in the old org (nor did it make sense for them to live there), a new org made the most sense - especially from a security point of view.
The old org has way, way too many approved members with push access, for which there was nothing I could do. This presented a pretty sizable security risk given that many packages in recent years have fallen victim to backdoors and the like due to lax security access.

Q: Was this approved?

Yes.^[archive]

Q: Do I need to worry about another migration sometime in the future?

No.

`v4.3.2`

Compare Source

Patch release 4.3.2

Caches enabled statuses on a per-logger basis to speed up .enabled checks (#799)

Thank you @omg!

jshttp/http-errors (http-errors)

`v1.8.1`

Compare Source

==================

deps: toidentifier@1.0.1

Custom tokenizer backend — replaced the prismjs npm package with a self-contained reprism-based grammar engine. ~11.5% faster tokenization on real projects (avg 1126 ms → 997 ms on a 548-file, 223-format scan).
Cross-format detection — Vue SFC (.vue), Svelte (.svelte), Astro (.astro), and Markdown files are now tokenized per-block/per-section. A <script> block in a .vue file can match a .ts file; a fenced code block in Markdown can match a .py file.
223 supported formats — Apex, CFML/ColdFusion, GDScript, Svelte, Astro, and 70+ additional languages added (up from 152). See FORMATS.md.
Shebang detection — extensionless executable scripts (e.g. /usr/bin/env python3) are auto-detected by their #! shebang line and tokenized in the correct language.
--store-path — configure a custom directory for the LevelDB cache, eliminating collisions when multiple jscpd processes run in parallel on the same machine.
--skipComments — shorthand flag for --mode weak, which strips comments before detection.
--formats-names — map specific filenames (e.g. Makefile, Dockerfile) to a detection format.

Bug Fixes

Entire-file duplicates silently dropped (@jscpd/core #728) — RabinKarp flushed the pending clone on a store hit at end-of-file instead of on a miss. Files that are complete copies of each other were undetected. Fixed.
ReDoS hang on Lisp/Elisp files (@jscpd/tokenizer #737) — the Lisp string regex /"(?:[^"\\]*|\\.)*"/ could catastrophically backtrack (O(2ⁿ)) on unterminated strings. Replaced with a linear /"(?:[^"\\]|\\[\s\S])*"/ pattern.
Process crash on malformed package.json (#739) — readJSONSync threw an unhandled SyntaxError when package.json contained invalid JSON, killing the process. Now emits a warning and continues with an empty config.
Vue SFC cross-file detection broken — the detector used the file-level format (vue) as the store namespace for all SFC blocks, preventing a <script> block in one .vue file from ever matching a <script> block in another. The namespace now reflects each block's resolved sub-format.
Vue SFC incorrect column numbers — tokens on the first line of a block carried block-relative column 1 instead of file-absolute column numbers. Fixed in @jscpd/tokenizer.
50 dependency security vulnerabilities remediated across the monorepo (Dependabot batches).

Known Limitations

Malformed SFC blocks (e.g. unclosed tags, invalid attributes) are silently skipped and do not contribute tokens.

`v4.1.1`

Compare Source

`v4.1.0`

Compare Source

New Features

AI Reporter — new ai reporter that produces compact, token-efficient clone output specifically designed for feeding results into language models and AI tooling. Use --reporters ai to activate it.
MCP Server enhancements — the Model Context Protocol server now exposes a jscpd://statistics resource and supports a recheck endpoint so AI agents can trigger a rescan without restarting the process.
Apex & CFML language support — jscpd can now detect duplicate code in Salesforce Apex and ColdFusion Markup Language (CFML) files (closes #83, #619).
GDScript support — detect copy-paste duplication in Godot Engine GDScript files.
HTML reporter footer — the HTML report now displays a branded footer with the jscpd version and a sponsor link.
--noTips flag — suppress the usage-tip messages that appear after a detection run.
CI: Node.js 22.x / 24.x — continuous integration updated to test against the latest Node.js LTS and current releases.

Performance

Tokenizer — grammars are now loaded lazily, hot paths are O(n), and the spark-md5 dependency has been removed in favour of a lighter built-in implementation. Startup time and memory usage are noticeably reduced on large codebases.
Replaced the vendored reprism syntax library with the official prismjs npm package, shrinking the installed footprint.

Bug Fixes

Restored the correct start.line expectation for weak-mode clone detection.

`v4.0.9`

Compare Source

`v4.0.8`

Compare Source

`v4.0.7`

Compare Source

`v4.0.6`

Compare Source

expressjs/morgan (morgan)

`v1.10.1`

Compare Source

===================

deps: on-headers@~1.1.0
- Fix CVE-2025-7339 (GHSA-76c9-3jph-rj3q)

add support for SIGINT on Windows (fixes issue #1720) (#1853) (500c1b0)

release-it/release-it (release-it)

`v19.2.4`

Compare Source

chore: update dependencies to resolve security vulnerabilities (#1273) (b45dd1a) - thanks @Yeom-JinHo!
Update a few dev deps (cd8acdc)

`v19.2.3`

Compare Source

Reuse generated changelog (316dbfa)
Remove obsolete eslint compat packages/config (f6cc8f3)
Update remark-preset-webpro and fix broken links (6e6dd4b)

`v19.2.2`

Compare Source

Improve getChangelog method (7a56364)

`v19.2.1`

Compare Source

Improve commit prompt (b7aca7c)
Remedy potential edge case in template helper (5c0a6ee)

`v19.2.0`

Compare Source

Add option to exit gracefully (e1f825d)
Update dependencies (424c9f6)
Auto-format docs (06f41bb)
fix: add shell mode for npm commands on windows (#1266) (382e346) - thanks @julienbenac!
Feat: Add publishPackageManager config option in NPM plugin to allow using different package manager for publishing (e.g. Bun) (#1169) (0dafc0b) - thanks @chrispader!
Only use --workspaces=false with npm (12bb89c)
Fix up docs/types a bit (05a5986)
Format (c9d6ebf)

`v19.1.0`

Compare Source

Ignore .npmrc (8ccd060)
Update lockfile (c4cd2ba)
Support interactive shell in non-CI mode for 2FA flow (resolve #1263) (a10b20d)
Add --workspaces=false to get rid of the null/matches error (14a4907)
Remove npm config env var warnings (b8c1247)
doc(readme): add release-it-beautiful-changelog plugin to list of plugins (#1261) (1b68c21)
Add 403 to consider resource alive (7969849)

`v19.0.6`

Compare Source

Update list of projects using release-it (92b49d3)
Bump github/codeql-action from 2 to 4 (#1253) (21309d3) - thanks @dependabot[bot]!
Bump actions/setup-node from 5 to 6 (#1255) (3fbaab1) - thanks @dependabot[bot]!
Test in node 24 (7a12b12)
Upgrade c12 (resolve #1254) (1f48d03)

Configuration

📅 Schedule: (in timezone Europe/Paris)

Branch creation
- "before 8am on monday"
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from e13033e to 627e8cb Compare November 5, 2025 18:33

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from a54c2a6 to 45a9389 Compare November 19, 2025 22:08

renovate Bot force-pushed the renovate/npm-dependencies-updates branch from 45a9389 to c786f29 Compare December 3, 2025 03:23

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from 21cc050 to c451ffe Compare December 16, 2025 22:13

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 3 times, most recently from 6336219 to 02bc510 Compare December 24, 2025 09:04

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from 88e81dd to 13fed5c Compare December 31, 2025 17:42

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 3 times, most recently from 764a39d to 6ca855a Compare January 11, 2026 09:39

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from f80b6ae to 79e5aee Compare January 19, 2026 19:40

renovate Bot force-pushed the renovate/npm-dependencies-updates branch from 79e5aee to d382d7a Compare January 20, 2026 22:11

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 3 times, most recently from ffb82b1 to b6c3047 Compare February 3, 2026 22:11

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from fc6e89e to 711fae9 Compare February 17, 2026 19:46

renovate Bot force-pushed the renovate/npm-dependencies-updates branch from 711fae9 to 036f81f Compare February 25, 2026 21:50

renovate Bot force-pushed the renovate/npm-dependencies-updates branch from 036f81f to dceb0f2 Compare March 5, 2026 15:15

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from 04c39a4 to 0fe4060 Compare March 13, 2026 21:00

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 3 times, most recently from 0ceaab5 to b439b9b Compare March 30, 2026 17:47

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from a811cef to 13b3222 Compare April 10, 2026 13:41

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 2 times, most recently from d555957 to cfefdcb Compare April 21, 2026 20:01

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 3 times, most recently from f775fec to 6eb5686 Compare April 29, 2026 19:28

renovate Bot force-pushed the renovate/npm-dependencies-updates branch 6 times, most recently from 113ccd2 to 468733a Compare May 15, 2026 21:23

fix(deps): update npm dependencies updates

ca4ab7a

renovate Bot force-pushed the renovate/npm-dependencies-updates branch from 468733a to ca4ab7a Compare May 17, 2026 12:29

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update npm dependencies updates#116

fix(deps): update npm dependencies updates#116
renovate[bot] wants to merge 1 commit into
developfrom
renovate/npm-dependencies-updates

renovate Bot commented Nov 3, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

Patch

What's Changed

New Contributors

Patch Release 4.3.3

Repository Migration Information

Q: What impact will this have on me?

Q: What are the security implications of this change?

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

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

Q: Why was the repository transferred?

Q: Was this approved?

Q: Do I need to worry about another migration sometime in the future?

Patch release 4.3.2

Breaking Changes

New Features

Bug Fixes

Known Limitations

New Features

Performance

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented Nov 3, 2025 •

edited

Loading