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.
Following up on #8462, I did a simple POC for a script that updates all the dependencies in the examples directories.
The intention is this would be triggered alongside
prepare-release.js
. It requires that the package versions are updated to work correctly.scripts/update-example-dependencies.js
:packages/*
directories, getting the current package version for eachpnpm-workspace.yaml
examples/*
looking for package.json, and updating with the values from 1 / 2@prisma/client
is updated, it triggers rebuilding GraphQL and Prisma schemas, which will avoid issues like 5311203To test:
examples/assets-local/schema.graphql
pnpm i
- this will fail due to missing file abovenode scripts/update-example-dependencies.js
pnpm i
- all should be fineTo improve:
fixPrismaPath
andexample-data
so that CodeSandbox worksAny feedback appreciated, I like these kinds of automations, but I know they're not popular with everyone - in my books they fall inside the reducing complexity category.