Skip to content

Latest commit

 

History

History
60 lines (42 loc) · 4.15 KB

ISSUES_RESOLVED.md

File metadata and controls

60 lines (42 loc) · 4.15 KB

Overview

This document is intended as a way to track issues that have been found that were particularly tricky to resolve. The intention of doing this is to help any other developer from taking a long time to resolve similar issues that they find.

Issues

Could not find \"store\" in the context of \"Connect(...)\"

At first it was thought that this had something to do with the I18 component used, but it was anything that was a container! So, this had something to do with using redux inside the rollup built library atoll-shared that was consumed by atoll-core.

Details

As soon as the Uncaught Invariant Violation: Invalid hook call originating in useMemo issue was resolved, this issue was encountered next.

{"status":"error","message":"Could not find "store" in the context of "Connect(withI18nextTranslation(App))". Either wrap the root component in a , or pass a custom React context provider to and the corresponding React context consumer to Connect(withI18nextTranslation(App)) in connect options.","stack":["Invariant Violation: Could not find "store" in the context of "Connect(withI18nextTranslation(App))". Either wrap the root component in a , or pass a custom React context provider to and the corresponding React context consumer to Connect(withI18nextTranslation(App)) in connect options.","at invariant (C:/Git/51ngul4r1ty/atoll-shared/node_modules/invariant/invariant.js:40:15)","at ConnectFunction (C:/Git/51ngul4r1ty/atoll-shared/node_modules/react-redux/lib/components/connectAdvanced.js:153:33)","at processChild (./node_modules/react-dom/cjs/react-dom-server.node.development.js:3090:14)","at resolve (./node_modules/react-dom/cjs/react-dom-server.node.development.js:3013:5)","at ReactDOMServerRenderer.render (./node_modules/react-dom/cjs/react-dom-server.node.development.js:3436:22)","at ReactDOMServerRenderer.read (./node_modules/react-dom/cjs/react-dom-server.node.development.js:3395:29)","at renderToString (./node_modules/react-dom/cjs/react-dom-server.node.development.js:3954:27)","at eval (webpack:///./src/server/middleware/serverRenderer.tsx?:26:90)","at Layer.handle [as handle_request] (./node_modules/express/lib/router/layer.js:95:5)","at trim_prefix (./node_modules/express/lib/router/index.js:317:13)"]}

Resolution

  • Stopped using npm link and instead used yalc (see TOOLS.md for details).

Uncaught Invariant Violation: Invalid hook call originating in useMemo

Details

Nothing was rendered and the stack trace displayed in the browser console was:

Uncaught Invariant Violation: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:

  1. You might have mismatching versions of React and the renderer (such as React DOM)
  2. You might be breaking the Rules of Hooks
  3. You might have more than one copy of React in the same app See https://fb.me/react-invalid-hook-call for tips about how to debug and fix this problem. at http://localhost:8501/static/vendor.7f3166c5.chunk.js:33239:26 at resolveDispatcher (http://localhost:8501/static/vendor.7f3166c5.chunk.js:33242:5) at useMemo (http://localhost:8501/static/vendor.7f3166c5.chunk.js:33297:20) at ConnectFunction (http://localhost:8501/static/vendor.7f3166c5.chunk.js:30349:75) at renderWithHooks (http://localhost:8501/static/vendor.7f3166c5.chunk.js:68791:18) at updateFunctionComponent (http://localhost:8501/static/vendor.7f3166c5.chunk.js:70608:20) at updateSimpleMemoComponent (http://localhost:8501/static/vendor.7f3166c5.chunk.js:70551:10) at updateMemoComponent (http://localhost:8501/static/vendor.7f3166c5.chunk.js:70468:14) at beginWork$1 (http://localhost:8501/static/vendor.7f3166c5.chunk.js:72233:16) at HTMLUnknownElement.callCallback (http://localhost:8501/static/vendor.7f3166c5.chunk.js:54030:14)

Resolution

cd atoll-shared run npm link ../atoll-core/node_modules/react

Useful Resource

https://reactjs.org/warnings/invalid-hook-call-warning.html