Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Next.js + Preact template uses `"react": "github:preact-compat/react#1.0.0"` in package.json but docs say v8+ should use preact/compat?
See original GitHub issueHi, sorry to clutter up your issues with silly questions but I was a bit confused about this one and couldn’t find much after Googling:
The docs for preact/compat state:
This module is for Preact 8.x and prior - Preact X includes compat by default. For Preact X, please uninstall preact-compat and replace your aliases with preact/compat.
I used the lovely reference implementation with @prefresh and aliases configured for Next.js, but I noticed that in package.json the React libs are aliased to preact-compat and not preact/compat (maybe because you can’t alias to a sub-module?)
I’m just curious whether this is correct or if I should change the alias library. Thank you, keep being awesome 😃
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think so. Both are using preact/compat v10 behind the scenes.
https://github.com/preact-compat/react/blob/1.x/index.js https://github.com/preact-compat/react/blob/1.x/package.json
https://github.com/preact-compat/react-dom/blob/1.x/index.js https://github.com/preact-compat/react-dom/blob/1.x/package.json
Ahh alright, understood now. Thanks everyone, clears up the confusion, appreciate the responses =)