You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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? :)
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.
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.
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.
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
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)
Activity
bjohansebas commentedon Feb 2, 2025
Hey @expressjs/express-tc, I’d like to work on the
expressjs/generatorto 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? :)
jonchurch commentedon Feb 3, 2025
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.
jonchurch commentedon Feb 3, 2025
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-updatesconfig for dependabot on a weekly cadence, to be able to catch new releases for security patches.jonchurch commentedon Feb 3, 2025
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.
ctcpip commentedon Feb 3, 2025
@bjohansebas for now, you can simply fork the session repo
jonchurch commentedon Feb 3, 2025
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
jonchurch commentedon Feb 3, 2025
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)