Closed wjram2133 closed 1 year ago
The page shows: Unhandled Thrown Error! Cannot read properties of undefined (reading 'some') TypeError: Cannot read properties of undefined (reading 'some') at CreateNimi (http://localhost:3000/static/js/bundle.js:4130:45) at renderWithHooks (http://localhost:3000/static/js/bundle.js:406739:22) at mountIndeterminateComponent (http://localhost:3000/static/js/bundle.js:410025:17) at beginWork (http://localhost:3000/static/js/bundle.js:411321:20) at beginWork$1 (http://localhost:3000/static/js/bundle.js:416284:18) at performUnitOfWork (http://localhost:3000/static/js/bundle.js:415553:16) at workLoopSync (http://localhost:3000/static/js/bundle.js:415476:9) at renderRootSync (http://localhost:3000/static/js/bundle.js:415449:11) at recoverFromConcurrentError (http://localhost:3000/static/js/bundle.js:414941:24) at performConcurrentWorkOnRoot (http://localhost:3000/static/js/bundle.js:414853:26) cd Hey developer wave
You can provide a way better UX than this when your app throws errors by providing your own errorElement props on
@wolframeth is this done?
The page shows: Unhandled Thrown Error! Cannot read properties of undefined (reading 'some') TypeError: Cannot read properties of undefined (reading 'some') at CreateNimi (http://localhost:3000/static/js/bundle.js:4130:45) at renderWithHooks (http://localhost:3000/static/js/bundle.js:406739:22) at mountIndeterminateComponent (http://localhost:3000/static/js/bundle.js:410025:17) at beginWork (http://localhost:3000/static/js/bundle.js:411321:20) at beginWork$1 (http://localhost:3000/static/js/bundle.js:416284:18) at performUnitOfWork (http://localhost:3000/static/js/bundle.js:415553:16) at workLoopSync (http://localhost:3000/static/js/bundle.js:415476:9) at renderRootSync (http://localhost:3000/static/js/bundle.js:415449:11) at recoverFromConcurrentError (http://localhost:3000/static/js/bundle.js:414941:24) at performConcurrentWorkOnRoot (http://localhost:3000/static/js/bundle.js:414853:26) cd Hey developer wave
You can provide a way better UX than this when your app throws errors by providing your own errorElement props on