[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [Feedback](/c/feedback/8) # Next.js non-informative errors and missing component context during build 12 views · 0 likes · 1 post Thomas Felder (@me-6815) · 2026-03-25 First of thanks to the team, IMHO you build the best stack. I have been seeing an increase in non-informative errors in the console output, however and just thought I’d send you some feedback about it. I’ve updated a context in `React` and every error during the build (and hot reload) points to completely irrelevant plumbing components which I have basically nothing to to with. I will find the error and I’m very happy with this framework overall. It would be great if you could take care to continue to output sensible info for debugging when builds fail. As an example of what we don’t want, I include some screenshots below. None of the errors even point to a component. Wish I could provide you with a commit or at least a bug report but unfortunately there’s nothing to go on. Nondescript errors are non-descript errors. Please please take care to keep them to a minimum. The errors I’m seeing include: > **TypeError: Cannot read properties of null (reading ‘useInsertionEffect’)** And: > **Invalid hook call. Hooks can only be called inside of the body of a function component.** The way I will debug this now is by commiting the code with the error and using `git diff` to determine what has changed. Best wishes, Thomas    PS: The problem was that my sass stylesheet said “:hovar” instead of “:hover”. Turbopack actually correctly identified the problem. Ditch webpack?