-
|
I'm maintaining a legacy project and preparing to migrate from redux to RTK. My web SPA is running in CEF, which uses Chrome 49.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
If you are targeting a legacy browser, you will probably add transpilation for your libraries as well as some polyfills to your stack. At that point you could also use RTK 2. The only feature that we use that cannot be transpiled away/polyfilled are Proxies, but those are already supported since Chrome 49. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply. So without transpiling the RTK library in my project by Webpack and Babel, or adding any polyfills, is it compatible with Chrome 49? I'm afraid a certain usage will break my application. |
Beta Was this translation helpful? Give feedback.
-
|
I have no idea. That said, with a target like that you should really use modern dependencies and transpile them - otherwise you will end up with a completely weird stack of unsupported legacy versions of dependencies (we won't ship any updates for RTK 1 anymore!). |
Beta Was this translation helpful? Give feedback.
I have no idea.
Chrome 49 is an 8 year old browser that was already outdated when RTK entered alpha five years ago and we definitely are not trying to support that target, but RTK 1 did support IE, so maybe it will.
That said, with a target like that you should really use modern dependencies and transpile them - otherwise you will end up with a completely weird stack of unsupported legacy versions of dependencies (we won't ship any updates for RTK 1 anymore!).