-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request: cloudflare worker support #316
Comments
I'm not sure where you draw the conclusion from that node_compat is discouraged? The docs don't mention any such thing: https://developers.cloudflare.com/workers/runtime-apis/nodejs |
@favna the wrangler CLI mentions that node_compat has serious tradeoffs also the plugin it uses is unmaintained |
Regarding Wrangler using code from ionic, you'll have to take that up with Cloudflare. As for the usage of That all said, I'm not sure if just replacing util is enough, because we also depend on: import get from 'lodash/get.js';
import fastDeepEqual from 'fast-deep-equal/es6/index.js';
import uniqWith from 'lodash/uniqWith.js'; And outside of bundling all the code into the shapeshift bundle I don't see any way to replace those. |
wrangler is also planning to use this plugin, maybe it'll solve the issue. see cloudflare/workers-sdk#3832 but they want to ship it as a breaking change so I am not sure if it'll happen anytime soon |
We only enabled it for browser environments as node already have it. We can still make it to bundle for node env too |
Is there an existing issue or pull request for this?
Feature description
From #248 I could gather that cloudflare worker support is something that was being kept in mind. I recently tried to use @discordjs/builders which depends on sapphire and it gave me errors for needing to enable node_compat, something I could gather is heavily discouraged
Desired solution
Implement an alternative for the inspect function imports from util
Alternatives considered
Find another package which provides the same functionality as the inspect function
Additional context
No response
The text was updated successfully, but these errors were encountered: