fix: revert "feat: migrate to preact/compat (#190)"
Description
This reverts commit 8c98f579b95992072474f02fe39865fda825379d from PR #190
Notes & open questions
I believe this was causing some issues in deployed environments.. I was also able to reproduce some errors locally with http-server and npm start.. Issues include:
not being able to find css/js assets consistently
CMD+SHIFT+R resulting in renderable content, CMD+R resulting in missing assets and failed loading
Apparently preact support is not quite where we need it with webpack 5, or we need to do some additional config. Considering the large reduction in final asset size, it was worth a try, but reverting now because potential pains & incompatibility are not worth it.
We can potentially investigate this further later, but we would need some way to reproduce these errors consistently and write some test to catch those failures.
Change checklist
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation if necessary (this includes comments as well)
[ ] I have added tests that prove my fix is effective or that my feature works
Title
fix: revert "feat: migrate to preact/compat (#190)"
Description
This reverts commit 8c98f579b95992072474f02fe39865fda825379d from PR #190
Notes & open questions
I believe this was causing some issues in deployed environments.. I was also able to reproduce some errors locally with
http-serverandnpm start.. Issues include:Apparently preact support is not quite where we need it with webpack 5, or we need to do some additional config. Considering the large reduction in final asset size, it was worth a try, but reverting now because potential pains & incompatibility are not worth it.
We can potentially investigate this further later, but we would need some way to reproduce these errors consistently and write some test to catch those failures.
Change checklist