(Possible) Infinite Loop caused by Context Provider(s)

[CharlestonREM]

Problem

An infinite loop (or infinite loops) seem to be occurring due to the unstable context value of one or multiple providers.

This project has 4 providers that I have created.

1. The Stepper Provider
2. The Available Products Provider
3. The Calculator Provider
4. The Modal Provider

Research & considering useMemo hook

All four of these providers employ React's useReducer hook. In a final note on useReducer in Hooks Api, there is a subheading labeled Bailing out of a dispatch

If you’re doing expensive calculations while rendering, you can optimize them with useMemo.

A question I don't currently have a clear answer to: what constitutes as an

expensive value

?

useMemo

• it returns a memoized value.
• memoization:

  • In computing, memoization or memoisation is an optimization technique used primarily to speed up computer programs by storing the results of expensive function calls and returning the cached result when the same inputs occur again. Memoization has also been used in other contexts (and for purposes other than speed gains), such as in simple mutually recursive descent parsing.[1] Although related to caching, memoization refers to a specific case of this optimization, distinguishing it from forms of caching such as buffering or page replacement. In the context of some logic programming languages, memoization is also known as tabling.[2]

[CharlestonREM]

similar issue with useReducer

https://github.com/facebook/react/issues/16537#issue-483790210

response

https://github.com/facebook/react/issues/16537#issuecomment-523771554

[CharlestonREM]

maybe the calculator provider &/or calculator component is causing the infinite loop...

[CharlestonREM]

is it vercel related? https://github.com/vercel/next.js/issues/6973

[CharlestonREM]

https://github.com/vercel/next.js/issues/6973#issuecomment-821500414

https://github.com/vercel/next.js/issues/6973#issuecomment-821508232

• [ ] consider implementing swr
• [ ] consider getting rid of loaded variable reference in context provider that is initialized via calculator...
• [ ] ask why initializing is required for a context (the only one i can think of is availableProducts context; but shouldn't this be separate from the calculator context? shouldn't the calculator ONLY calculate via passed parameters?