Skip to content

2026-02-25 Express Working Session #478

Closed

Description

@github-actions

Date/Time

Timezone Date/Time
America/Los_Angeles Wed, Feb 25, 2026, 01:00 PM
America/Denver Wed, Feb 25, 2026, 02:00 PM
America/Chicago Wed, Feb 25, 2026, 03:00 PM
America/Bogota Wed, Feb 25, 2026, 04:00 PM
America/New_York Wed, Feb 25, 2026, 04:00 PM
UTC Wed, Feb 25, 2026, 09:00 PM
Europe/London Wed, Feb 25, 2026, 09:00 PM
Europe/Madrid Wed, Feb 25, 2026, 10:00 PM
Europe/Paris Wed, Feb 25, 2026, 10:00 PM
Europe/Warsaw Wed, Feb 25, 2026, 10:00 PM
Europe/Moscow Thu, Feb 26, 2026, 12:00 AM
Asia/Kolkata Thu, Feb 26, 2026, 02:30 AM
Asia/Shanghai Thu, Feb 26, 2026, 05:00 AM
Asia/Tokyo Thu, Feb 26, 2026, 06:00 AM
Australia/Sydney Thu, Feb 26, 2026, 08:00 AM

Or in your local time:

Agenda

Extracted from top priority labelled issues and pull requests from expressjs/discussions prior to the meeting.

Invited

  • @expressjs/express-tc
  • @expressjs/triagers
  • @expressjs/security-wg

Observers/Guests

This meeting is open for anyone who wants to attend. Reminder to follow our Code of Conduct.

Joining the meeting


Please use the following emoji reactions in this post to indicate your
availability.

  • 👍 - Attending
  • 👎 - Not attending
  • 😕 - Not sure yet

Activity

  1. kjugi commented on Feb 25, 2026

    @kjugi
    Member

    I think agenda was untouched. We have discussed this PR instead: expressjs/express#6404

  2. bjohansebas commented on Feb 26, 2026

    @bjohansebas
    Member

    @kjugi what was discussed about that?

  3. blakeembrey commented on Feb 26, 2026

    @blakeembrey
    Member

    The consensus was that it probably won't land. There's a couple of reasons:

    1. This breaks existing users for little benefit (e.g. new URL() currently works).
    2. It's an overall change to the design of Express' APIs - if you look at any other method, you'll see they all accept anything and rely on coercion to correct types.

    The conversation itself broke down into two classes of issues. The first is whether we should have validation at all, and the majority take was no (we should only validate if it'd otherwise result in an invalid state, not because someone is using the API with something they shouldn't be, the goal of the framework is to be minimal with low overhead), and the second was whether we should be coercing things to make them work (e.g. non-strings into strings) which was more contentious.

    The main split of opinion seemed to be on maintainer burden, with the exhaustion on APIs that accept anything making it hard on maintainers, vs breaking existing users who might be using an API successfully with something that we don't expect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions