[custom-builds-rc] handling of configuration options that don't work in modules mode

[xortive]

• text_blobs
• wasm_modules added by Add wasm_modules config field for bundling arbitrary WebAssembly modules. #1803

These options do not have meaning in modules mode. It is unclear what module path we should use for them, as they may not be inside upload_dir. We should warn if they are present when in modules mode.

[ItsiAdam2]

This should definitely error and explain that imports should be used instead. I would also suggest that documentation is created to explain how to properly use WASM in modules, rather than the dated and obscure templates.

[stale]

This issue has been automatically marked as stale because it has not had recent activity in the last 180 days. It will be closed if no further activity occurs in the next week. Please feel free to comment if you'd like it to remain open, and thank you for your contributions.

[admah]

Thanks for reporting this issue! Wrangler v1 is now deprecated and support is only being provided for critical updates or security concerns. As such, we are closing this issue.

New versions of Wrangler are maintained in the workers-sdk repo. If you are running into a similar issue with wrangler v2, please report it in the workers-sdk repo. For more info about wrangler v1 deprecation, please check out our blog post.