Some frameworks may require a different package for an async runtime which is likely not much of an issue however there may be others, in particular the typescript land, where some may want to run on node, or bun, or deno or something else that is more than just a simple package import.
This may require splitting them up in dockerfiles and creates more maintenance, more files to deal with. Ideally, each framework is run as intended to gain and present its capabilities within the limited scope of this project but perhaps there isn't much difference at least within the scope of this project so it's unclear if it's worth implementing.
Some frameworks may require a different package for an async runtime which is likely not much of an issue however there may be others, in particular the typescript land, where some may want to run on node, or bun, or deno or something else that is more than just a simple package import.
This may require splitting them up in dockerfiles and creates more maintenance, more files to deal with. Ideally, each framework is run as intended to gain and present its capabilities within the limited scope of this project but perhaps there isn't much difference at least within the scope of this project so it's unclear if it's worth implementing.