settimeout | setTimeout as a Service | Monitoring library

If you're using a button or HTML element to trigger your function, you can simply do this:

It's always better to use promises. An implementation of this functionality could be;

Rather looks like the Leaflet CSS is incorrectly loaded in your production bundle: tiles are scrambled up, no zoom and attribution controls.

UPDATE:

For your firebase_core version is seems to be sufficient to pass the FirebaseOptions once you initialize firebase in your flutter code (and you don't need any script tags in your index.html):

Usually, this warning shows up when:

• The parent (currently App) component updates very often and causes WebDisplay component to re-render. In the provided snippet, every 30 milliseconds;
• At least one prop passed to RenderHTML is referentially unstable between each re-render. In the provided snippet, tagsStyles reference changes on every re-render.

Notice that between every update of the App component caused by the useEffect hook, the html prop passed to WebDisplay is unchanged. But WebDisplay is re-rendered anyway because it is not "pure".

For this very reason, a pretty straightforward solution is to wrap WebDisplay in React.memo:

This appears to be a known fact according to Github discussions.

One of the comments, which I thinks is pretty self explanatory:

React currently will batch state updates if they're triggered from within a React-based event, like a button click or input change. It will not batch updates if they're triggered outside of a React event handler, like a setTimeout().

React internally uses unstable_batchedUpdates(). You can pass in a callback function and state updates inside that will be batched. This does not happen automatically for timeouts, promises, and async functions. So they are called from outside the callback and state updates inside them are not batched.

Right now react only batches sync setStates inside event handlers. But in react 18 it will be available in setTimeout, useEffects etc Here is excellent explanation from Dan https://github.com/reactwg/react-18/discussions/21

Looks like you're not defining the type in the questions array. This line is defaulting every input field to text because it couldn't find the type.

inputField.type = questions[position].type || 'text'

Normally useEffect and its cleanup are called asynchronously (on another stack) after render. But if you call setState in a timer and there are useEffect callbacks, they are invoked eagerly but all accumulated state change from cleanup is called after setState that invoked this operation.

So in your example when setTimeout handler is called:

• when calling setA: a state is changed and two state changes from cleanup are added to pending state change queue
• when calling setB: first valueB is applied to b and then null from the cleanup (it's kind of batched here)

This tries to imitate the behaviour when state updates are actually batched like in click handlers (first apply state updates from the click handler and then from useEffect).

You can see what's happening more clearly when you use updater functions: