Use versions in examples for workspace packages along with pnpm overrides #771
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add all workspace packages to root package.json overrides to ensure local packages are always used during development - Update example package.json files to use ^0.0.0 version ranges instead of workspace: protocol - This allows gitpick installations to work while pnpm overrides ensure examples use local workspace packages during development
- Update all remaining examples to use ^0.0.0 version ranges - Replaces workspace:* and workspace:^ with version ranges that accept any 0.x version - Ensures gitpick installations work while pnpm overrides force local workspace packages during development
|
kevin-dp
requested changes
Nov 6, 2025
Contributor
kevin-dp
left a comment
kevin-dp
left a comment
There was a problem hiding this comment.
^0.0.0 does not work as you expect. It restricts to exactly version 0.0.0.
From the docs:
Caret Ranges ^1.2.3 ^0.2.5 ^0.0.4
Allows changes that do not modify the left-most non-zero element in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.
I think you want * or latest
Replace ^0.0.0 with >=0.0.0 <1.0.0 in all examples. ^0.0.0 only matches exactly 0.0.0, not any 0.x version. The explicit range >=0.0.0 <1.0.0 correctly matches any 0.x version while preventing major version bumps.
Collaborator
Author
|
Ok this looks good then https://jubianchi.github.io/semver-check/#/%3E%3D0.0.0%20%3C1.0.0/1.0.0 — then we can update to 
|
More templates
@tanstack/angular-db
@tanstack/db
@tanstack/db-ivm
@tanstack/electric-db-collection
@tanstack/offline-transactions
@tanstack/powersync-db-collection
@tanstack/query-db-collection
@tanstack/react-db
@tanstack/rxdb-db-collection
@tanstack/solid-db
@tanstack/svelte-db
@tanstack/trailbase-db-collection
@tanstack/vue-db
commit: |
Contributor
|
Size Change: 0 B Total Size: 79.8 kB ℹ️ View Unchanged
|
Contributor
|
Size Change: 0 B Total Size: 3.34 kB ℹ️ View Unchanged
|
kevin-dp
approved these changes
Nov 6, 2025
KyleAMathews
deleted the
claude/gitpick-examples-install-011CUrmuw3rm7wnB2AJRKSQC
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running examples in the monorepo, we want to ensure they use they actual workspace code and don't pull from npm — we use pnpm overrides for this. This PR adds all workspace packages to the overrides list.
When running examples outside of the monorepo (we suggest
gitpickfor this). We want proper versions that have the example pull the latest published version from npm. We had some packages withworkspace:*versions which wouldn't work anymore outside of the monorepo. So this PR moves all versions to use ^0.0.0 to get the latest version in the 0 range.