-
Notifications
You must be signed in to change notification settings - Fork 199
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
Error when upgrading from Chart.js 3.0 to 4.4 #150
Comments
We have the same issue @biren34, any update on this did you manage to solve the issue above? Thank you so much. |
It seems to be due to incomplete datasets defaults for the library and some assumptions Chart.js makes on the default property values, working on it and releasing a new patch soon, it will require a breaking change to the configuration of the financial charts datasets. |
I face this issue when I do This is the error I get:
I see that @santam85 submitted a PR which is reviewed with no conflicts. So if it is merged to master and released on npm then that would be really helpful for all. **Temporarily for now I have installed the |
@santam85 I tried but, the dist folder was missing after Since the actual files are missing, my console keeps showing bunch of errors. (I have now switched to different charting library because of the reoccurring compatibility issues between chart.js and it's plugins and react wrapper integrations.) |
Please have a try with v0.2.0, you'll need to change your dataset options in accordance to what is shown in the updated examples. |
First, thank you for this great candlestick plot.
I downloaded the example and was able to get it running with my data. I then tried to upgrade to chart.js 4.4 by changing the include in index.html from <script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/chart.js"></script> to <script src="https://cdn.jsdelivr.net/npm/[email protected]/dist/chart.umd.min.js"></script>.
I now get an "Uncaught TypeError: String.prototype.toString requires that 'this' be a String" error, with a pretty unhelpful call stack:
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: