Not compatible with the new ES6 module worker format #174
Comments
Same here, trying to implement the new custom builds in Vitedge but all calls to |
can you link me to this? Tagged this as |
@signalnerve i've patched the immediate roadblocker in the above PR #188 - please have a look if that's a suitable fix. |
Note I merely patched the crash blocking us, but a proper solution would probably pass the env object as a third parameter or similar. however i didn't want to mix this fix with a necessary discussion about how to change the public API going forward. would be nice if this could be released as a fix asap, at least in some esm branch on npm as it complicates the build process for us. |
Related wrangler issue: cloudflare/wrangler-legacy#1938 |
For one method, |
Please have a look at my PR, I introduce a fix for this problem. Sadly, the following problem will still cause problems when you try to deploy your site: |
We're cutting a release on both wrangler and kv-asset-handler that should provide a path forward. I'll send a PR documenting how very soon. |
released, with the readme updated, we'll update the official docs as well soon. |
It seems that this package still has the assumption of the old worker format (e.g. global environment variables,
FetchEvent
, etc) and does not work properly with the new ES6 module format. I would like to use Durable Objects, which requires the new ES6 module format, in a Workers Site project, andwrangler
already has a patchset for Workers Site support with the new ES6 module format, and the fact that this package does not support the new format seems to be the last blocker.The text was updated successfully, but these errors were encountered: