3 ms·
This seems cool, and probably aimed at a specific use case. Maybe if you're just starting out on joining a team? My question is if there's something I'm not se
by ramon156 2y ago
This seems cool, and probably aimed at a specific use case. Maybe if you're just starting out on joining a team?
My question is if there's something I'm not seeing. How often do people have to do this for it to be a tool? Why couldn't I just check the package.json myself?
Or is this aimed at LLM's, so you can run a program instead of letting an LLM guess the tech?
- dangsux 2y ago[dead]
- manvillej 2y agopackage.json does not capture all the technologies in a repository. just the JS ones. This seems to capture full stack technologies. This would be very helpful when evaluating existing projects either as a consultant, new team member, open source, or evaluating a vendor's codebase or project.
- h1fra 2y agoyes it's one of the main use case, discovering and documenting at scale. Even on nodejs project there is more than just the package.json