aleph start produces react error 321
See original GitHub issue> aleph start
INFO Compiling...
INFO - bundle
INFO {} polyfill.js (ES2015) • 9KB
INFO {} deps.js • 160KB
INFO {} shared.js • 431B
INFO {} /pages/index.js • 5KB
INFO {} main.js • 385B
INFO Server ready on http://localhost:8080/
500 - Minified React error #321; visit https://reactjs.org/docs/error-decoder.html?invariant=321 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
> aleph --version
aleph.js 0.3.0-alpha.22
deno 1.8.2
v8 9.0.257.3
typescript 4.2.2
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Invariant Violation: Minified React error #321 #16029 - GitHub
I had to comment the following code in order to solve the #321 error, similar to development config. ... Now it works when...
Read more >Hard dealing with Error: Minified React error #321 - ReactJS
After a lot of debugging, I discover that the problem was caused by certain functions of the library mdbreact
Read more >Error: Minified React error #321 - WordPress.org
Whenever I write a useEffect() inside a component function of my block plugin, the edit page goes blank and the console logs the...
Read more >sitemap-1.xml - LogRocket Blog
... https://blog.logrocket.com/javascript-either-monad-error-handling/ ... https://blog.logrocket.com/getting-started-with-create-react-app-d93147444a27/ ...
Read more >error importing React component from published package
I built a package that exports React components. ... Minified React error #321: error importing React component from published package.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@TranquilMarmot try deleting the .aleph folder and reloading everything, deno might be using a cached old version of something.
maybe it was caching different versions of react.