Latest release is completely broken
See original GitHub issueIt looks like there was an update to the minification script which caused all variables to be renamed, which probably was to save some extra bytes in the package. However, it renamed all the exports, and it also renamed “exports” as well, so now the package exports an empty object, which causes anything using preact to fail completely. Here’s how the main export looks, built from the latest release directly:
For now, we are pinning to 8.2.7
, which fixes the problem. Probably something should be done about this quickly, as it’s a fairly critical issue.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:9 (6 by maintainers)
Top Results From Across the Web
latest release completely broken :( · Issue #3 · declarativesystems ...
INFO:kivy:[CutBuffer ] cut buffer support enabled INFO:__main__:starting docker_init in own thread DEBUG:docker.auth.auth:Trying paths: ...
Read more >LATEST 2022 VERSION BROKEN ALL
Auto complete is broken. ALL IS BROKEN! ... This issue is read only, because it has been in the Closed - Fixed state...
Read more >Firefox Release 97 8th Feb Completely Broken on My System ...
Long story short, today I received v97. Firefox would no longer open websites. Settings would not open. about:config would not open.
Read more >Screentime is unusably broken on iOS 16 - Apple Community
Announcement: Introducing the latest version of the world's most advanced ... It is infuriating to see Apple release completely broken software - how...
Read more >Windows 10 completely broken - Microsoft Community
Unplug power and remove battery, press and hold power button for 30 seconds to release all power from circuitry, plug back in and...
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
@leeoniya I’d certainly be open to it - Sam did a bunch of experimentation and got things set up with GCC a while back in #564.
might also want to consider switching to https://github.com/google/closure-compiler-js, it’s much slower (several seconds vs dozens of ms) but the bundles end up smaller and with fewer regressions, in my experience.