add Wrangler 'find_additional_modules' documentation

[petebacondarwin]

Summary

Adds documentation for missing Wrangler configuration

Documentation checklist

• The documentation style guide has been adhered to.

[hyperlint-ai]

2 files reviewed, 3 total issue(s) found.

[hyperlint-ai]

2 files reviewed, 2 total issue(s) found.

[GregBrimble]

I know it's not strictly related to your change, but I wonder if it's worth just calling out somewhere on this page that automatic bundling is what makes TypeScript possible. It's not actually obvious when we say stuff like "TypeScript is a first-class language on Cloudflare Workers" elsewhere in the docs.

This is especially important if we're making module discovery more accessible. It should be really clear that these modules need to be given to us as ESM/CJS/Wasm/Text or Data.

[irvinebroque]

ty @petebacondarwin for docs, few notes re: dynamic imports behavior at runtime

[irvinebroque]

Even if you upload these as separate modules, don't we still have an issue?

cloudflare/workerd#2372

Or am I misunderstanding the problem there?

cc @jasnell

[petebacondarwin]

There is definitely still a cost, since as I understand it, we do parse all modules at start up. The main difference, unless I am mistaken is that we don't execute the code in the lazy module until it is imported.
Despite this, we found that next-on-pages start up time was improved dramatically by splitting out chunks from the main entry-point, so there is some benefit.
Also, once we update the implementation in workerd this will become significantly improved, so things can only get better if you use this approach.

[petebacondarwin]

I know it's not strictly related to your change, but I wonder if it's worth just calling out somewhere on this page that automatic bundling is what makes TypeScript possible. It's not actually obvious when we say stuff like "TypeScript is a first-class language on Cloudflare Workers" elsewhere in the docs.

This is especially important if we're making module discovery more accessible. It should be really clear that these modules need to be given to us as ESM/CJS/Wasm/Text or Data.

Actually, I think an even better solution would be for us to be able to run non-ESM JavaScript/TypeScript additional modules through esbuild to ensure they are also in the right state for consumption by workerd.

[GregBrimble]

Actually, I think an even better solution would be for us to be able to run non-ESM JavaScript/TypeScript additional modules through esbuild to ensure they are also in the right state for consumption by workerd.

There's definitely some code lying around somewhere for a "process entrypoint"/"bundle no-bundle" sort of thing which could be used. Interesting idea. And I guess --no-bundle still works as the opt-out. Yeah, could be explored!

[irvinebroque]

Thank you Pete!!!