Adjusts bundler output to work with Node.

[gunsch]

💸 TL;DR

Adjusts bundler output to also work with Node.

📜 Details

• In Node, require calls are wrapped in a function that provides modules and exports. Redefining them caused the app to not load.
• Deleting the src.replace line modified here fixed Node, but broke runtime-lite, which needs those definitions shimmed in.
• The resulting code is a compromise that works in both cases, at the cost of an ugly var in the generated code. Sorry about that.

🧪 Testing Steps / Validation

• Testing a simple Devvit with Play that registers a custom post until I got it to fully load and render the post!

[niedzielski]

thanks for this beefy comment and PR message. I didn't understand why var specifically was needed--it's hoisted outside the block but why? some issue with @devvit/public-api? I know the code is cryptic by nature but I see it and immediately think it's safe to rewrite `"use strict"; module.exports ??= {}; const {exports} = module; }\n'. anything you can do to make this clearer would be appreciated.

the other thing I was thinking is that changing app code is hard but changing runtime-lite or the compute @devvit/public-api bundle is possible if wanted.

[logan]

When we load a cjs file into a module in node, the contents are basically wrapped like this:

(function(exports, require, module, __filename, __dirname) {
// Module code actually lives in here
}); 

[gunsch]

beefiness++

added more comment, hopefully that explains better

we could change runtime-lite and drop this src.replace call entirely, though that's a little outside the scope I wanted to dig into. we can't fix this on the compute side though without some ugly Node hackery (i.e. monkey-patching the contents of require('module').wrapper)