Temp fix graphql mesh (bad upgrade) #3733
Merged
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 wrong release versions in @graphql-mesh... see ardatan/graphql-mesh#5377
The idea is to only install
as deps.
Drawback: Size in consuming apps (node_modules/lambda size) - consuming apps does not need to have all of that when the use the dist (vercel has standalone that will probably remove most the unused code)
By analyzing the dist folder... we actually should have these package installed (as peers or direct dependencies of api-gateway). But it will be harder to maintain with npm-check-updates or renovatebot... Cause some of them have been published to v1.0.0 and actually their latest versions is lower.
Todo need to see how pnpm will work