Chris de Almeida

Do you mean like, in the case where it's e.g. an unused transitive dependency? So that the fact the library doesn't work at all doesn't matter, thus the breakage via...

sure I agree -- but I think the consideration is unchanged. it hinges on the definition of what makes a package "completely broken". I am thinking like, new node module...

Based on what we agreed, it goes in the next major, but we don't release a major only for an engines field update. So if something else is going out,...

hmm.. looking at [the changes](https://github.com/pillarjs/finalhandler/blob/master/HISTORY.md#unreleased), this appears to be a no-op for end users. seems odd to do a major rev at this point, but whatever works!

[This proposed ADR](https://github.com/expressjs/discussions/pull/365/files) carves out the question of environment support, so that this ADR can focus on CJS vs ESM rather than runtime/env support.

this is done! 🙏

`cookie` can probably already today be imported into ESM cleanly, no?

Express TC met today and agreed we don't want to pursue ESM exports. - We don't find the stated motivation compelling. - It's extra work and maintenance for little benefit,...

until then, it would be great if we could help our users with low vision to be able to use the site 😊

related: CVE Schema issue: Formalize versionTypes - https://github.com/CVEProject/cve-schema/issues/362