Was getState() replaced or removed; is it now built in behavior?

Trying to continue using window.snapSaveState = () => getState(); with the new version @loadable/components, and it seems to not be a module export anymore.

I have a purely static react app and have been using react-snap in conjunction with your guy’s beautiful getState 😃

How should I continue to maintain this functionality with @loadable/components?

[stereobooster]

Here are options for anyone who will face this issue:

• use react-loadable@2.3.3
• wait for React’s ConcurrentMode
• use unstable_ConcurrentMode (at your own risk). Here is full example https://github.com/stereobooster/react-async-issue
• create PR for @loadable/component, which will add back getState

[stereobooster]

If we would drop the tone, there is a sense in those words.

Alright let’s be realistic and don’t expect real help free labor from react-snap and from loadable-components people on the internet who don’t owe you anything.

Yes, this is open source. People provide you with results of their labor for free without any warranty or further promises. You can use, you can skip it. It is up to you.

If you want to create a pre-rendered static website with dynamic loading don’t waste spent your time (sad but true…): just leave loadable-components and react-snap and go something like Gatsby.js.

Right, and you can spend your time to learn GraphQL (which is good in long-term, I guess, but will slow down you in the beginning) and spent some time writing transformation layer from the existing data source to Gatsby’s GraphQL.

---

Gatsby is a great tool and if you can use it (like you already know how to use it), go ahead and use it. From my experience, it has some barrier for novice users, like GraphQL and a need to write custom plugins to work with your data.

React-snap is for a different purpose, it is for the case when you already have some codebase and don’t want to invest time to rewrite in Gatsby or react-static or …

As of loadable-components, I use the previous version which has getState(). My hope is that eventually we will not need any external solution and will be able to use React.lazy, which is not the case right now.

I tried:

const RootApp = (
  <ConcurrentMode>
    <Suspense fallback={<div>Loading...</div>} maxDuration={5000}>
      <App />
    </Suspense>
  </ConcurrentMode>
);

if (rootElement.hasChildNodes()) {
  ReactDom.hydrate(RootApp, rootElement);
} else {
  ReactDom.render(RootApp, rootElement);
}

and

const root = ReactDom.unstable_createRoot(rootElement);
root.render(<Suspense fallback={<div>Loading...</div>} maxDuration={5000}><App /></Suspense>);

The code above results in white flash (blink), but logically it shouldn’t