1. Feedback
  2. React
  3. 48664

Welcome to the React feedback portal. We’re happy you’re here! If you have feedback on how to improve the React, we’d love to hear it!

  • Check out the features or bugs others have reported and vote on your favorites. Feedback will be prioritized based on popularity.
  • If you have feedback that’s not listed yet, submit your own.

Thanks for joining our community and helping improve Syncfusion products!

1
Vote

Component Packages Incompatible with the new Vite 5 and SSR

Since updating to the new Vite 5 (Using Remix), components fail to render server-side leading to  React errors:
"

Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports."


From the new Vite 5 migration guide:

Vite 5 now removes the .default and .__esModule handling to match the production behaviour. In practice, this shouldn't affect properly-packaged dependencies.

Note that these changes matches the Node.js behaviour, so you can also run the imports in Node.js to test it out. If you prefer to stick with the previous behaviour, you can set legacy.proxySsrExternalModules to true.


I can confirm that changing the Vite settings to the legacy way of handling imports, the Syncfusion React components load fine.

Have a look here: 

https://vitejs.dev/guide/migration#ssr-externalized-modules-value-now-matches-production