dynamic imports are no fun because you lose typing

Yeah, a lot of libraries expect that. Sometimes, you just gotta rewrite it yourself

Depending on how the library works, you can do things like

--define SOME_VAR=foo

to replace things in code at build time

So if it's looking for

process.env.API_KEY

, something like

--define process.env.API_KEY="foo"

should work (or could be accomplished with a custom build)

ooooh, what's this feature?

is this wrangler?

Yeah this is wrangler. Though any build tooling (esbuild, webpack, etc.) all have some way of doing "defines" like that

https://developers.cloudflare.com/workers/wrangler/commands/#publish - scroll down a bit to

--define

It's effectively wrapping this: https://esbuild.github.io/api/#define

oh nice!

so I can have the secret in my github secrets and bundle it into my code at build time

@James is that across the entire bundled code? so I could use it to replace strings in dependencies too?

I think so

I've not tested outside of user code tbh

do you know if it works with dev mode?

it does yeah. It should be documented on that same page under

dev

too

nice!

will have a play, should get me a long way toward forcing some packages to work

awesome, good luck 😄

obviously relies on the thing you're replacing to be globally unique..

which shouldn't be a problem if it's some kind of

process.env['FOO']

thing

yeah, true

and I could also use it to nuke

import { URL } from "node:url";

although not clear on how the syntax deals with spaces

I'd probably reach for a custom build if you do anything complex. We have stuff like this with an esbuild config for example:

define: {
    'process.env.NODE_ENV': JSON.stringify('production')
},

I've never tried using it to nuke imports like that - I'm not sure that'd work - would depend on if this happens before or after bundle 🤔

What’s with the stringify?

copy/pasta and trimmed. It's more complex than that in real code, but you have to wrap it in quotes, so that when it's inlined you get

"production"

and not just

production

otherwise your code will treat

production

as a literal and complain it's undefined

you could also just do

'process.env.NODE_ENV': '"production"'

here

but I pulled that from a large code snippet that does more stuffs