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
{{ message }}
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
On the Express TC meeting we discussed testing for our dependencies, especially for v5 and were thinking we need a better way to integrate groups of modules to CITGM. What do other frameworks do for this?
I believe someone released a package for testing dependencies of any npm project recently. I'll have to find that or maybe someone else remembers what it was called
one of the idea / question that came up for discussion is: how frameworks can better leverage CITGM. For example, if a class of test can be (dynamically?) organized in such a manner that a set of modules that depend on the framework is selected and tested, and accounted together? that way, we will be testing those modules for node.js stability, as well as the stability of the framework, in one shot, against a target node.js version.
This would be of great value for frameworks before they release their majors?
We could clone and maintain a copy of the test suite that fits the frameworks' purpose, or decide to reuse the existing CITGM, if it already is capable of catering to this use case.
@andrewhughes101 is currently looking at what we thought step one would be - which was how can framework authors get the list of modules that depend on them, and filter them down in a useful way.
We chatted about this a bit on todays meeting, and wanted to get feedback from folks on the @nodejs/web-server-frameworks team on the work being done on this tool:
I know this one is old, but I am thinking that we should put together a list of action items which need to be addressed to get express back into CITGM. Not sure if we should use this issue or make a new one. Going to add the agenda tag so we can discuss.
Activity
gireeshpunathil commentedon Mar 19, 2020
Just thinking loud in terms of what those could be:
?
Ethan-Arrowood commentedon Mar 19, 2020
I believe someone released a package for testing dependencies of any npm project recently. I'll have to find that or maybe someone else remembers what it was called
[-]Disucss modules in CITGM[/-][+]Discuss modules in CITGM[/+]gireeshpunathil commentedon Mar 19, 2020
one of the idea / question that came up for discussion is: how frameworks can better leverage CITGM. For example, if a class of test can be (dynamically?) organized in such a manner that a set of modules that depend on the framework is selected and tested, and accounted together? that way, we will be testing those modules for node.js stability, as well as the stability of the framework, in one shot, against a target node.js version.
This would be of great value for frameworks before they release their majors?
We could clone and maintain a copy of the test suite that fits the frameworks' purpose, or decide to reuse the existing CITGM, if it already is capable of catering to this use case.
BethGriggs commentedon Mar 19, 2020
We've had similar discussions in the package maintenance WG:
@andrewhughes101 is currently looking at what we thought step one would be - which was how can framework authors get the list of modules that depend on them, and filter them down in a useful way.
wesleytodd commentedon May 28, 2020
We chatted about this a bit on todays meeting, and wanted to get feedback from folks on the @nodejs/web-server-frameworks team on the work being done on this tool:
pkgjs/wiby#1
It is very early, but feedback on if the direction seems useful, would be helpful to keep it going in the right direction.
EDIT: forgot the context!
This tool will help module authors test their downstream packages. So you can test your upcoming releases with packages which depend on you.
wesleytodd commentedon Jan 30, 2024
I know this one is old, but I am thinking that we should put together a list of action items which need to be addressed to get
expressback into CITGM. Not sure if we should use this issue or make a new one. Going to add the agenda tag so we can discuss.