unmet peer dep issue w/ tanstack/router-cli
There is a minor issue when installing (at least w/
pnpm
)
Most likely, this is usually a benign issue (since most releases of tanstack/* packages are "so that all sub-packages are on the same semver"). And it's also not an issue if you always stick to the latest version. But there might be some edge-cases where this will break something, right?
The expected behavior would be for @tanstack/router-cli
to require @tanstack/router-generator
in the same version as itself. But looking at the distributed package.json
for 1.121.27
(current) we see
Which means it accepts higher versions too.
But since router-generator
then also has react-router
in its dependencies, it's likely users will have an "unmet peer" dep issue, since they probably install router-cli
and react-router
, but not router-generator
7 Replies
robust-apricot•3mo ago
if you can clean up the package dep structure, you are invited to do so 😆
blank-aquamarineOP•3mo ago
ah ah
is there a script somewhere that "increments the semver" for all packages at once?
Actually, I think the fix might be as simple as this
according to the
pnpm
docs on publishing (https://pnpm.io/workspaces#publishing-workspace-packages)
So for example, if we have foo, bar, qar, zoo in the workspace and they all are at version 1.5.0, the following:
Will be transformed into:
robust-apricot•3mo ago
can you create a PR for this?
blank-aquamarineOP•3mo ago
robust-apricot•3mo ago
oh I thought this only affects one package
blank-aquamarineOP•3mo ago
I think I noticed a couple of them, but likely this is a strategy that should either be adopted for all packages or not at all
robust-apricot•3mo ago
cc @Sean Cassiere