Rekit studio Doesn't work in IE11

[joacim-boive]

Empty project IE11 in Edge mode When built open localhost:6075

rekit create test-app --sass

Using ReKit 2.20:

Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props, _owner, _store}). If you meant to render a collection of children, use an array instead.

Using Rekit 2.30 handleIndexRoute C:/Users/jobo15/IdeaProjects/ecster-login/rekit-labb/src/common/routeConfig.js:31 28 | return; 29 | } 30 |

31 | const indexRoute = route.childRoutes.find(child => child.isIndex); 32 | if (indexRoute) { 33 | const first = { ...indexRoute }; 34 | first.path = ''; View compiled ./src/common/routeConfig.js C:/Users/jobo15/IdeaProjects/ecster-login/rekit-labb/src/common/routeConfig.js:42 39 | route.childRoutes.forEach(handleIndexRoute); 40 | } 41 | 42 | routes.forEach(handleIndexRoute); 43 | export default routes; 44 | 45 |

I think it's a polyfill problem but haven't found the cause yet.

[supnate]

Thanks @joacim-boive for reporting this! But please just use Chrome! Thanks! 😂

[joacim-boive]

What I meant to say is that code generated using Rekit Studio doesn't work in IE11. Hence Rekit Studio doesn't work either.

Most people can probably live with that Rekit Studio doesn't work, but probably not that the generated code doesn't work in a common browser.

Anywho, I located the problem although I'm not entirely sure why the fix works:

By moving babel-polyfill from webpack-config.js / entry.dev.dll.dev-vendors to the top of entry.dev.main it works fine. Even Rekit Studio seems to work as well.

I'm guessing it's because the order the js is generated as the polyfill needs to come first.

[supnate]

Sorry for the mis-understanding. Yes it's sure that the generated app should support IE11 from Rekit Studio side. I will look at the issue with a Windows machine then. Thanks for your investigation!