Doc versioning + ReactLiveScope #7272
Unanswered
M1chaelChen
asked this question in
Q&A
Replies: 1 comment
-
|
Hi Unfortunately I don't think it is easy to do that, and you'd be better using a different site per lib version (you don't have to follow the 1 SPA for multiple versions that Docusaurus uses by default, see how older Docusaurus versions are archived as separate sites for example) Note: React < 17 is not really designed to be run alongside other React versions in the same app See also https://reactjs.org/blog/2020/08/10/react-v17-rc.html#changes-to-event-delegation |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, we have a regular doc site setup with ReactLiveScope that imports the design system packages we built. Now we are planning to add versioning but then realize that the packages imported in ReactLiveScope will all point to the same version. Is there a way to configure different live scope package versions for different doc versions? For example, for doc version 1.1.0, I want live scope to use React 16, and for doc version 1.2.0, I want it to use React 18.
Would appreciate any help here.
Beta Was this translation helpful? Give feedback.
All reactions