-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change react version #734
Milestone
Comments
Thanks @Ajaesuria, fair point, 16.2 is pretty old itself at this point - @plotly/dash-core perhaps we should add a react version |
@Ajaesuria this issue should be resolved with the ongoing PR #868 (target release dash 1.2.0) the react version is now 16.8.x and a dev version react is used when you set debug=True. |
HammadTheOne
pushed a commit
to HammadTheOne/dash
that referenced
this issue
May 28, 2021
HammadTheOne
pushed a commit
to HammadTheOne/dash
that referenced
this issue
May 28, 2021
* remove \dontrun and use interactive() * ✏️ add single quotes for CRAN
HammadTheOne
pushed a commit
that referenced
this issue
Jul 23, 2021
HammadTheOne
pushed a commit
that referenced
this issue
Jul 23, 2021
* remove \dontrun and use interactive() * ✏️ add single quotes for CRAN
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good day.
In my private project I need to use react above 16.2 and dash-renderer only use 15.4 or 16.2. Also, it will be nice if dash included a develop version of react when go live to spot errors more easily.
Is there an easy way to change dash-renderer instead of each time a virtualenv is installed go inside the packages and manually setting it or I will need to fork dash-renderer and only install my custom version?
I just asking because I want to keep up with the changes in the master.
The text was updated successfully, but these errors were encountered: