ultra VS react-loadable

Another option is ultra.

Ultra is another option if you want to use Deno with React: https://ultrajs.dev

Ultra Docs

In answer to your specific question of "can it replace my current npm + web pack workflow". The answer is more complex. Can you use npm? For the most part yes. Can you use Webpack specifically? That I'm not sure of, but there are a number of tools that occupy the same niche in the Deno ecosystem such as Packup as well as full-brown server/client frameworks like Fresh and Ultra

I hear you but a lot of devs refused to use Deno because it did not support npm. If you want to develop npm-free use Ultra: https://ultrajs.dev

If you really want SPA, Ultra(https://ultrajs.dev) is a good choice.

Take a look at Ultra (http://ultrajs.dev) and throw away most of your build tools. If you need to compile SCSS to CSS, try denosass (https://github.com/hironichu/denosass).

In this article, you’ll learn about a new React framework called Ultra, which uses Deno and React and focuses on using web streams and native features within the browser.

I think you were looking at one of the ancillary repos like create-ultra-app and not the main repo here: https://github.com/exhibitionist-digital/ultra

Website: https://github.com/jamiebuilds/react-loadable

React Loadable: This library makes it easy to split your React code into smaller, lazy-loaded chunks that can be loaded on demand. This can significantly improve the initial loading time of your application, especially for large and complex apps. https://github.com/jamiebuilds/react-loadable

I have a very simple React component that uses react-loadable to dynamically import another component. The code looks something akin to the following:

react-loadable - A higher order component for loading components with promises

It's very important that you are choosing an active project instead of a dead/unmaintained project. An active project improves over time through community feedback. An unmaintained project does not move forward, fix functional bugs or patch security issues. Sometimes, a very popular package can be abandoned and go into a "frozen" state with many open issues and pull requests. It might have been a great solution in the past, but this is a sign that we have to move on. An example is react-loadable. It was a great solution for a very long time for code-splitting in React. I totally loved it. But it's stale now with many issues and PRs since 2018 (this post is written at the end of 2021). Now, if I need to split code in React, I use loadable-components, which is in active development, becoming more popular, patches bugs reported by the community, and most importantly, solves my problems. My personal advice: choose a package that's active in the last 3-6 months, with issues that are being resolved and PRs that are being merged.

Preloading is possible with react-loadable: https://github.com/jamiebuilds/react-loadable#preloading