Skip to content

Upgrade "content-type"#728

Merged
Phillip9587 merged 5 commits into
masterfrom
be/upgrade-content-type
May 13, 2026
Merged

Upgrade "content-type"#728
Phillip9587 merged 5 commits into
masterfrom
be/upgrade-content-type

Conversation

@blakeembrey
Copy link
Copy Markdown
Member

The parser in content-type@2 is 3x faster and doesn't throw anymore.

Copy link
Copy Markdown
Member

@Phillip9587 Phillip9587 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! But we need to also update it in type-is and express to not duplicate the module in the dependency tree: https://npmgraph.js.org/?q=express#select=content-type%401.0.5

@blakeembrey
Copy link
Copy Markdown
Member Author

😓 Oh damn I missed it was used in this package, since it's still support node 0.6 and has a hard API to work with I guess it's a good candidate to start refactoring. If/when I release the new type-is should I bump it in this PR or a new one?

@Phillip9587
Copy link
Copy Markdown
Member

I think it does not matter and it is up to you if you but it in a separate PR. I would prefer a single PR for body-parser and one for express.

@blakeembrey
Copy link
Copy Markdown
Member Author

@Phillip9587 Released type-is@2.1.0 with content-type@2, bumped the version of type-is in this PR.

Comment thread lib/utils.js Outdated
Comment thread lib/utils.js Outdated
blakeembrey and others added 3 commits May 13, 2026 10:59
Co-authored-by: Phillip Barta <barta.phillip@gmail.com>
Co-authored-by: Phillip Barta <barta.phillip@gmail.com>
Copy link
Copy Markdown
Member

@Phillip9587 Phillip9587 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for all the work @blakeembrey

@Phillip9587 Phillip9587 merged commit 37f36a2 into master May 13, 2026
17 checks passed
@Phillip9587 Phillip9587 deleted the be/upgrade-content-type branch May 13, 2026 18:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants