Cloudflare change Node Imports to supported node: prefix #741
Conversation
This file contains 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
|
All commit authors signed the Contributor License Agreement. |
Jumaron
changed the title
|
Hi, any news on this ? |
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.
Currently it is not possible to use Edgedb-js natively with Cloudflares Pages with there Edge network (Cloudflare Workers).
The Problem of this, are most likely connected to the imports, which cannot be found for the Workers since we need to add coresponding to Cloudflare: https://developers.cloudflare.com/workers/runtime-apis/nodejs/
The node: prefix.
The main point of this, is also to discuss future improvement on the integretation of Cloudflare Pages, which is one of the most popular Edge deployment methodes.