More strict check for node version for graphql-upload
#2235
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.
I'm working on a
apollo-server-flyio
package to use in fly.io apps. The fly app environment is not node, it's much closer to the browser, which means no access tofs
, which meansgraphql-upload
blows up on require.This PR makes the Node version check more strict — if there are no node process details it avoids requiring the
graphql-upload
package for non-node runtimes. This is useful for me, obviously, but should also improve the Cloud Flare worker build experience and help with any future Deno efforts.TODO: