Should we archive this?

[UlisesGascon]

WDYT @wesleytodd?

Seems like never was published on npm 🤔

[wesleytodd]

Ah, yeah this was one of my efforts to decouple the more sub components of express. The only reason I can come up with for not archiving it is if this would enable us to work on removing the req/res prototype shenanigans in a way that would not block progress in express. I only am just now seeing your issue, so let me think on it a bit more before we decide what to do.

[wesleytodd]

So I looked around and tried to remember why I started with this one and IIRC I picked it because it had no internal dependencies and so could easily be lifted out wholesale. Additionally, it has most of the surface area for end-user needs for someone "building your own" express.

My thinking was that we served multiple purposes by extracting request and response from the core packages:

1. allows it to be used outside of express
2. simplifies the surface area inside express itself
3. follows the pattern with router and others that were extracted
4. allows for it to evolve ahead of express majors

This last point is one where I am still unsure if it is a good idea, there are certainly pros/cons. So all in all I am undecided if this is a good idea. Let me post this in the #express channel and see if anyone else has opinions before we take an action.

[ctcpip]

it simplifies in some ways and adds complexity in other ways

follows the pattern with router and others that were extracted

what was the reasoning for extracting router and others?

at the end of the day, if there's compelling reasons to do, we should do it. if not, then archive.

I tend to be in the monorepo camp until and unless there are strong reasons to modularize, mainly due to increased maintenance burden

[UlisesGascon]

So... Should we archive this or not? 🤔

[UlisesGascon]

I will finally archive it based in the Slack discussion.