Skip to content

Conversation

@Phillip9587
Copy link
Member

Upgrading type-is to v2 aligns with express v5, which depends on type-is v2. This alignment prevents duplication of the type-is package in node_modules.

@socket-security
Copy link

New and updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] 🔁 npm/[email protected] None +3 272 kB wesleytodd

View full report↗︎

@bjohansebas
Copy link
Member

Would this cause any breaking changes? Looking at the history of type-is, it contains the following notes:

  • Remove ambiguous extensions from IANA for application/*+xml types
  • Update primary extension to .es for application/ecmascript

@wesleytodd
Copy link
Member

Specifically for body parser I dont think it will cause issues. I read the same changelog before approving and probably should have said that in a comment, sorry.

@Phillip9587
Copy link
Member Author

Sorry I checked when i created the PR, but I should have documented it in the PR description.

@wesleytodd wesleytodd merged commit 23dc867 into expressjs:master Jan 16, 2025
9 checks passed
@Phillip9587 Phillip9587 deleted the type-is-v2 branch January 17, 2025 08:36
@UlisesGascon UlisesGascon mentioned this pull request Jan 23, 2025
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.

3 participants