Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Usage with Vitejs
See original GitHub issue💬 Questions and Help
Hello, we recently had to migrate a huge Webpack app over to Vitejs. And the fact is that in the Webpack version we were using loadable-components. But because of its dependency on Webpack for SSR we decided that we were gonna disable it temporarly. But now, we would like to try and hook it up with Vite so that it works without problem.
So that question is: does loadable-components work or has any plans to work with Vite?
If not, the limitation right now is the SSR piece with the babel plugin as well as the chunks collector? If so, could you point us towards a possible solution? We could very much provide some PR if needed even.
Thanks!!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hey. Unfortunately
loadable-componentscurrently are very webpack specific. There are plans to make it less bound to the underlying system, but this is not something you can expect to happen soon enough.Currently, the only “browser-independent” code splitting solution is react-imported-component, which I do maintain as well, but it hasn’t been tested with Vite, so no guarantees as well.
Vite is gaining in popularity, I hope this stance can be reconsidered.