Aral Roca Gomez
Aral Roca Gomez
Hi @fpapado, thank you for the answer. In my case, I'm doing an e-commerce with Next.js `8.1.0`. With next.js, the first loaded page is loaded using SSR, and the rest...
I just realized that I can pass the `loadEagerly` as `loadEagerly={!process.browser}`to only use it in SSR, serve the image asap, and then, check the error using the `error` prop after...
@fpapado currently I'm using the first workaround that I commented, with `onError` event. However, to fix the SSR problem that I told (when the event is fired before hydration) I...
Better detailed: **hook**: ```jsx import { useRef, useCallback, useEffect } from 'react' import noop from 'lodash/noop' /** * Using loadEagerly, with SSR the image is displayed ASAP, * in the...
Please, activate again this 🙌
I have the same issue with webpack 5
Installing `webpack` to the project solve it... `npm i webpack@latest --save-dev`
This is because you need to charge first scrollMonitor.js
@midudev is not possible to share context values between Progressive hydration parts like, for example, for `I18nProvider`?: I'm looking for something like: ```jsx {/* FIRST PROGRESSIVE HYDRATION SECTION */} {/*...
It works in a read-only context as you said. I've put before the example of `I18nProvider` custom provider but maybe is not so clear, my bad. In my case, I...