Discuss a runtime-loading companion for the web-framework example #1111

I maintain CompatLab, which records npm import/require results across pinned Node.js, Bun and Deno versions.

Package Phobia’s web-framework examples help answer “what would this dependency cost to install?” Someone evaluating the same dependency for a runtime migration also needs to know whether their import loads. Would a short companion example in that README section be useful?

For a concrete case, Express 5.2.1 here can be paired with its completed loading report. The October 9 execution passed the root import and require checks on Node 24.21.0/26.10.0, Bun 1.4.2 and Deno 2.9.7, on Linux amd64. It did not test HTTP routing, middleware or application behavior.

I’m proposing a small explanatory link for that example first. Coverage is still limited, so a link on every package result could send readers to missing evidence. There would be no API dependency or background scans. If this fits the project, I can prepare the documentation change; if runtime checks are outside its scope, that is useful to know too.