Replies: 3 comments 2 replies
-
|
It sounds like you might be looking for Changesets: https://turborepo.com/docs/guides/publishing-libraries#using-changesets-with-turborepo |
Beta Was this translation helpful? Give feedback.
-
|
I'm looking for turbo support here. I don't want to redefine package dependencies in a separate file. They're already listed in package.json and that's the turbo graph. So I'd like to reuse it. If changesets had package.json deps lookup support... then maybe. But that's literally turbo. |
Beta Was this translation helpful? Give feedback.
-
|
Changesets also does what you're describing. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe there's something I can do w/ turbo query, but I'm unable to find a way to filter the query command, and it doesn't seem to work in CLI mode. I.e. |
Beta Was this translation helpful? Give feedback.
-
|
Another hacky solution that technically works for my usecase, but isn't robust at all: find ./packages -maxdepth 2 -mindepth 2 -name "package.json" \
-exec grep -q "@foo/bar" {} \; -print \
| sed -e 's|/package\.json$||' -e 's/^/-F /' \
| xargs turbo bump-patch |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Hi guys,
So I have the following monorepo setup where
/packages/*has tons and tons of packages that are all intricately intertwined and are then published into npm registry. The problem that I'm running into is that when I want to do amajor/minorversion bump to a package, I need to do apatchversion bump to all packages that depend on it.For the same of example lets say I have:
where the dependencies are as:
ui-utils->utils->core.So what I thought I could do was
turbo bump-patch -F ...{./packages/core} -F "!./packages/core"followed byturbo bump-major -F ./packages/core. But that doesn't work because it bumps all dependencies, includingui-utilswhich I don't want to bump, because it doesn't require a new version.There's no
turbo bump-patch -F ...{./package/core} --traverseDepth=1from what I can tell. Is there a workaround? It's very tedious to update dozens of packages and their changelogs manually every time a new package version is needed and feels like an obvious thing turbo should be good at helping with.Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions