Skip to content

2025-02-03 Express TC Meeting #328

Closed

Description

@github-actions

Date/Time

Timezone Date/Time
America/Los_Angeles Mon 03-Feb-2025 12:00 (12:00 PM)
America/Denver Mon 03-Feb-2025 13:00 (01:00 PM)
America/Chicago Mon 03-Feb-2025 14:00 (02:00 PM)
America/New_York Mon 03-Feb-2025 15:00 (03:00 PM)
Europe/London Mon 03-Feb-2025 20:00 (08:00 PM)
Europe/Amsterdam Mon 03-Feb-2025 21:00 (09:00 PM)
Europe/Moscow Mon 03-Feb-2025 23:00 (11:00 PM)
Asia/Kolkata Tue 04-Feb-2025 01:30 (01:30 AM)
Asia/Shanghai Tue 04-Feb-2025 04:00 (04:00 AM)
Asia/Tokyo Tue 04-Feb-2025 05:00 (05:00 AM)
Australia/Sydney Tue 04-Feb-2025 07:00 (07:00 AM)

Or in your local time:

Agenda

Extracted from tc agenda labelled issues and pull requests from expressjs/discussions prior to the meeting.

Invited

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

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

Links

  • Minutes:

Joining the meeting

Activity

  1. bjohansebas commented on Feb 2, 2025

    @bjohansebas
    Member

    Hey @expressjs/express-tc, I’d like to work on the expressjs/generator to support Express 5 and land several PRs in that repository, I know there are people using it, and probably change the name to create-express.

    Could you also give me access to the session repository so I can work on version 2? :)

  2. jonchurch commented on Feb 3, 2025

    @jonchurch
    Member

    Im working through the agenda and checking on items.

    We've got a few that have been carried over for a while now. Is there anything actionable for these items in this meeting? They seem more like discussion items that decision items.

  3. jonchurch commented on Feb 3, 2025

    @jonchurch
    Member

    We discussed the dependabot PR, and agreed that Ulises can continue to work on that. He understands the concern of the group, which are noisey dependabot updates, using a caret for our own deps and being a library means that dep updates aren't really useful for us. I noted that we could investigate the security-updates config for dependabot on a weekly cadence, to be able to catch new releases for security patches.

  4. jonchurch commented on Feb 3, 2025

    @jonchurch
    Member

    From wes v5 minor update (associated issue expressjs/express#6316):

    Cookies signature, tj/node-cookie-signature#36, there is a desire from the current maintainer to release the project and have it find a new home. We are okay taking it into the org.

    finalhandler, there's some landed but unreleased changes. We are discussing adding engines and revving a v3. We don't have breaking changes in the v2 line, if you consider us supporting v18 for node as of 2.0 (which we documented but without engines). Wes proposes not major revving, leave the engines field PR open. We decided to go with wes' proposal (and we must delete the existing engines field which is wrong, it is set to >= 0.8.

  5. ctcpip commented on Feb 3, 2025

    @ctcpip
    Member

    @bjohansebas for now, you can simply fork the session repo

  6. jonchurch commented on Feb 3, 2025

    @jonchurch
    Member

    ESM Topic. We have an open ADR about this #323

    We need to do more async discussion on this, we aren't saying that we'll block ESM but it can read that way.
    Blake mentioned that we can call out that CJS is required, but ESM is optional

  7. jonchurch commented on Feb 3, 2025

    @jonchurch
    Member

    Generator. Wow this is due for a bigger discussion. We are not sure we want the maintenance burden in the team. So there's a door open for folks around the project/ecosystem to work together to make something (which sounds like fun)

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