Seems to be caused by #13582

If you're not using getRequestEvent(), then you don't need to worry about this. If you are using it, then you should set the nodejs_compat flag, as mentioned in the warning.

@eltigerchino I think you were mentioning some way we could deal with this by having the adapter influence the configuration of the deployment? https://developers.cloudflare.com/workers/wrangler/configuration/#generated-wrangler-configuration

I'm not using getRequestEvent(), so it doesn't affect me (and I don't want/have the nodejs_compat flag).

But I still like to have clean logs without warnings :-)

@eltigerchino I think you were mentioning some way we could deal with this by having the adapter influence the configuration of the deployment? developers.cloudflare.com/workers/wrangler/configuration#generated-wrangler-configuration

Yes, that was the initial idea but it seems that generating a wrangler configuration is prone to getting out of sync with the user config if they don't re-run the build. Instead, the Cloudflare folks suggested adding an error message if the appropriate flags aren't set. Otherwise, we need to look at trying to treeshake this import away if the getRequestEvent() function isn't used.

I'd highly recommend enabling the nodejs_als compatibility flag in the meantime if you want to get rid of the warning. This doesn't seem to bundle any extra code in the worker from my testing compared to enabling the nodejs_compat flag which does.