daveymoores

9 ms·

1.
by daveymoores 1mo ago
Nice, I've seen this before. Are you getting much traction within the cross-repo space? From personal experience, I know that the vast majority of products are poly-repo setups with often a monorepo core plus APIs, SDKs etc that sit ou
2.
by daveymoores 1mo ago
How do you build the call graph? Is it language agnostic? I have a tool - https://carrick.tools - that works just in the Typescript space and extracting and reliably constructing the call graph has been a really complex problem
3.
by daveymoores 1y ago
tRPC works within the context of a monorepo and provides utilities for type safety, typically between frontend/backend. Carrick allows you to check API producers/consumers across different repositories. It isn't a library for
4.
by daveymoores 1y ago
Hi HN, I’m David, introducing Carrick. For a while I’ve been thinking about how traditional CI is blind to the world outside its own repository. A change in one service can silently break another, and you often don't find out until it&
5.
Show HN: Carrick – Automated API Validation Across Microservices(carrick.tools)
2 points by daveymoores 1y ago|3 comments
6.
by daveymoores 1y ago
I've been working on a GitHub Action that checks producers and consumers of APIs and catches mismatches in CI across repositories. Rather than contract testing, this uses SWC to extract the routes from express apps/mounted routers
7.
Using an LLM and SWC to find API breaking changes across repos(carrick.tools)
1 points by daveymoores 1y ago|1 comments
8.
Show HN: Autolog – Git-powered timesheets for freelancers(autolog.dev)
1 points by daveymoores 1y ago|0 comments