Issues with Suspense/lazy in Preact 10.0.1
See original GitHub issueI am using Parcel + TypeScript + Preact and when i upgraded from Preact version 10.0.0 to 10.0.1 I started to get an error with Suspense.
Uncaught (in promise) TypeError: Cannot read property 'indexOf' of null
at t (suspense.js:64)
All that changed was the patch version of Preact. I have a repository showing the issue and my settings here: https://github.com/nrdobie/preact-10.0.1-issue. The master
branch uses 10.0.0
and broken
branch uses 10.0.1
Main Packages Versions:
parcel-bundler@1.12.4
typescript@3.6.4
preact@10.0.1
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Suspense for Data Fetching (Experimental)
Suspense is not a data fetching library. It's a mechanism for data fetching libraries to communicate to React that the data a component...
Read more >preact-suspense-lazy-issue
VS Code's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VS Code. Manage Extension.
Read more >Code splitting with React.lazy and Suspense - web.dev
Another feature of Suspense is that it allows you to suspend multiple components from loading, even if they are all lazy loaded. For...
Read more >cypress-io/cypress - Gitter
hi everyone, I've got a question / issue. I've got an app using React and React Suspense, and React.lazy() that I'm testing with...
Read more >Complete Guide to React Lazy Loading and Code Splitting
React Suspense is a react component that lets components “wait” for something before rendering. Today, React Suspense only supports one use case ...
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 FreeTop 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
Top GitHub Comments
Fix has been PR’ed, thanks for the reproduction this helped me to tackle the problem. It’s a bit of a bad luck one to be fair. The thing is that it wasn’t safe for
_suspensions
to exist without mangling this would mean that terser is safe to mangle it to whatever it wants which can interfere/be overwritten.This has now been pinned to
__u
.@darklight9811 Please file a new issue for this if you want it to be resolved. Notifications on closed issues are pretty invisible in GitHub’s UI, because by default only open issues show up when clicking on the
Issues
tab. Nobody will browse through all closed issues to see if someone made a comment in some closed issue. Please file a new issue.