Is there an "official" way to have production/deve...

# webassembly

[chrisjenx]

Is there an "official" way to have production/development env/distribution? seems like there is no way to pick development/production compilation/distribution targets?
This seems not like the best/but only way... https://gist.github.com/CameronProbert/85b7d60fa9572d93566f5c5ee62441e0

[turansky]

Browser? Node.js?

[chrisjenx]

Browser

[chrisjenx]

So jsBrowserDistribution

[turansky]

Do you want to have 1 bundle, but run it in different and use it different envs?

[turansky]

Or you want to build 2 separate (production/development) bundles?

[chrisjenx]

two different bundles, or at least be able to define different environment (host/port) for distribution vs running locally

[turansky]

In webpack you can use DefinePlugin to solve this problem.

[turansky]

We used it previously for the same problem.

[turansky]

https://webpack.js.org/plugins/define-plugin/

[chrisjenx]

Yeah so have to do webpack stuff instead of just being able to have two kotlin srcs

[turansky]

Bundler is more powerfull - it will process all sources

[turansky]

I have multiple libraries, where I use same flag

[chrisjenx]

How does the bundler know what I'm targeting tho?

[chrisjenx]

As there is only one task in gradle

[chrisjenx]

or is distribution always production?

[turansky]

distribution is production by default

[chrisjenx]

I see

[turansky]

You can change mode in common case

[turansky]

We use Vite and Vite supports it by default

[turansky]

3 separate property-files

.env
.env.production
.env.development

[turansky]

Webpack can have similar plugin 🙄

[chrisjenx]

I see ok, yeah was just hoping to try and keep it all in kotlin/gradle, but I guess this is the only really decent way right now 😞

[turansky]

DotEnv probably will fit better

[turansky]

(less js code)

[chrisjenx]

Yeah I think I saw that, you have a default then a .env.production from what I understand?

[turansky]

Yes, but it's not how it works in DotEnv (as I see)

[turansky]

I have Gradle-only solution for you too

[chrisjenx]

Oh cool, that would be preferable, we really only need to tweak the hostname and port, nothing crazy

[turansky]

You can add filters for Sync tasks

[turansky]

Complex example

[turansky]

Main idea:
1. You have Sync tasks IncrementalSyncTask for both modes
2. You can add custom sync task berore it and replace content with default filter. I created custom, because my case is complex
3. PROFIT

[chrisjenx]

dang lol, I think I did something like that a while back for some jvm resources

[chrisjenx]

This might be a nice addtion for your plugin btw, sure theres others struggling with the same thing

[turansky]

We use KFC, which already provides Vite support for Kotlin/JS

[chrisjenx]

oh cool

[turansky]

One more Gradle option - add Vite support for WasmJS in KFC 😉

[turansky]

sure theres others struggling with the same thing

🧌

[chrisjenx]

Well coming from Android where you can just dump things into BuildConfig or resources and create different build types, kinda cumbersome jumping between build systems

[turansky]

cc @Michael Porotkin

[turansky]

@chrisjenx I added wasmJs target support to KFC.
Now you can use Vite with wasmJs target too.
Are you ready to try? 😉

[turansky]

With .env OOB support 😜