Why was `kotlin-redux` module removed from the wra...

# react

[Robert Jaros]

Why was kotlin-redux module removed from the wrappers project? @turansky

[Robert Jaros]

Neither redux nor react-redux projects seem to be deprecated.

[turansky]

1. No users were expected
2. Major releases were missed
3. Low quality of declarations
4. For Redux users - RTK looks like preferred option
5. ...
cc @Sergei Grishchenko

[turansky]

Do you use them directly?

[Robert Jaros]

Yes. I have a redux module in kvision.

[turansky]

Copy declarations - is it option for you?

[Robert Jaros]

I'm releasing a major release so I can drop the module. But I was curious why it was removed.

[turansky]

Yes, it looks like best option.

[Robert Jaros]

btw. "No users were expected" sounds funny 🙂

[turansky]

No PRs, no issues

[Robert Jaros]

Because it just works 🙂

[turansky]

No questions in chat

[turansky]

We receive questions about things, which works prerfect on 90%

[turansky]

Quality of Redux declarations is smaller and no questions

[Robert Jaros]

Ok, thanks for the info.

[Robert Jaros]

I'm also using kotlin-react and kotlin-node if you ever think about removing these two as well 😉

[turansky]

We also use them ;)

[turansky]

Other legacy packages marked in README (3 subprojects)

[turansky]

Sorry for the inconvenience 😞

[jschneider]

Removal of react-redux hit us unprepared... Just to fill in the "no-user-info"...

[turansky]

UPDATE:
Subprojects removing doesn't look like big problem
You can still use fixed versions:

dependencies {
    implementation("org.jetbrains.kotlin-wrappers:kotlin-redux:4.1.2-pre.785")
    implementation("org.jetbrains.kotlin-wrappers:kotlin-react-redux:7.2.6-pre.785")
}

[Florent Martin]

We are also using KotlinJs and Redux-Wrapper for a web-app, but we are strongly thinking about moving to Typescript+Vite because of this kind of unpredictable changes and the very slow hot-reloading.

[turansky]

We already have Vite bundler support in KFC plugins.
Vite dev server support is in progress.

[Robert Jaros]

@turansky Any thoughts on supporting wasmJs with KFC plugins?

[turansky]

Do you mean Vite bundler support for wasmJs?

[Robert Jaros]

Yes

[turansky]

We need browser declarations for WasmJs for start 😉

[Florent Martin]

ViteJS in KFC Plugins 💥 That sounds great!
Thx @turansky

[turansky]

We already checked Vite Dev - it works fine 😉
Single problem for now - conflict with default Kotlin/JS tasks.

[turansky]

Driver of Vite activity - @Michael Porotkin ;)

[turansky]

@Robert Jaros In latest KFC we added KotlinViteDevTask , which supports custom Vite config.
As result - you can use it even for WASM ;)

[turansky]

In latest KFC - jsViteTask is available.
All known problems fixed 😉

cc @CLOVIS

[CLOVIS]

👀

[CLOVIS]

What's your approach to make it work?

[CLOVIS]

My plugin generates the vite.config.js file, and it works with the default KJS config. I see this one requires es15 and per-file?

[turansky]

My plugin generates the vite.config.js file

What if I need additional plugin?

[turansky]

I see this one requires es15 and per-file?

Header should be renamed - it's defaults, which plugin will set

[turansky]

Motivation for es15 :
1. Less bundle
2. More readable JS code
3. It's future default

[CLOVIS]

What if I need additional plugin?

You can declare it

[CLOVIS]

The DSL is in its own artifact if you want to reuse it: https://opensavvy.gitlab.io/automation/kotlin-vite/api-docs/vite-base/index.html

[turansky]

Config copying works fine 🙂

[CLOVIS]

How do you insert the config you need into it then?

[turansky]

There is no such problem 😉
We just provide env property with main JS file path - you can use it, if it's what you need.

[turansky]

In common case you can use any entry path.

[turansky]

@CLOVIS Update. Per-file required for faster vite dev work 😉

[CLOVIS]

Is there any docs on how to use the plugin? It's very vague to me what it can or can't do

[Florent Martin]

I tried to use ViteJS with new KFC Plugins but didn’t understand how to either

[CLOVIS]

@Florent Martin don't hesitate to try mine 🙂 https://opensavvy.gitlab.io/automation/kotlin-vite/api-docs/vite-kotlin/index.html

[Florent Martin]

@CLOVIS Yes it is the plan for now

[CLOVIS]

If you have any feedback, we have our own channel: #C078Z1QRHL3