fix #3030 and run relateive test in edge-runtime #3036
+86
−54
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.
This pr intends to fix the inconsistent behavoir of swr's
hash
in edge-runtime dev mode.The reason for this problem is because we're using
node.js
to simulate theedge-runtime
for local developmentThe global
Array
andObject
of edge-runtime are injected fromnode.js
and the JS engine does not use global Array/Object constructor while building an array/object literal.Then in dev mode
So we need find alternative to determine whether a key is an array or a
plain object