Uncaught TypeError: model.positioner is not a function

[sreejithqb]

Hello thank you for your plugin and latest update.
We have a small problem from 0.2.0 update, after the update we are getting the error and labels are missing from the chart.

**

Uncaught TypeError: model.positioner is not a function
Uncaught TypeError: model.positioner is not a function
at coordinates (chartjs-plugin-datalabels.js:359)
at Object.afterDatasetDraw (chartjs-plugin-datalabels.js:618)
at Object.notify (Chart.min.js:10)
at t.drawDataset (Chart.min.js:10)
at t.drawDatasets (Chart.min.js:10)
at t.draw (Chart.min.js:10)
at t.render (Chart.min.js:10)
at Object.callback (Chart.min.js:10)
at Object.advance (Chart.min.js:10)
at Object.startDigest (Chart.min.js:10)
at Chart.min.js:10
**

[simonbrunel]

Hi @sreejithqb, sorry for that. Can you build a jsfiddle that reproduces this issue and/or share the page that doesn't work anymore?

[simonbrunel]

From your stack trace, it doesn't seem to match 0.2.0:

• at coordinates: v0.2.0/chartjs-plugin-datalabels.js:359
• at Object.afterDatasetDraw: v0.2.0/chartjs-plugin-datalabels.js:618

But still 0.1.0:

• v0.1.0/chartjs-plugin-datalabels.js:359
• v0.1.0/chartjs-plugin-datalabels.js:618

[sreejithqb]

Ok. So https://cdn.jsdelivr.net/npm/chartjs-plugin-datalabels will not pull the latest version?

[simonbrunel]

https://cdn.jsdelivr.net/npm/chartjs-plugin-datalabels pulls the latest version if it's not cached by the browser but it's definitely not a good practice as warned in the docs and in the jsDelivr docs:

Requesting the latest version (as opposed to "latest major" or "latest minor") is dangerous because major versions usually come with breaking changes. Only do this if you really know what you are doing.

There is nothing we can do on our side, I think clearing your cache will fix the issue. I would recommend you to always use a fully versioned URL in your project in production environments:

https://cdn.jsdelivr.net/npm/[email protected]

[simonbrunel]

Though, I don't understand why you get this error because even if it still uses 0.1.0 (cached), it should work. But I can't investigate further without a test case that reproduces that issue.

[sreejithqb]

Thanks Simon. We will check the issue in detail. We are using Angle Theme for Angle. I Think it is a cache issue

[simonbrunel]

@sreejithqb did you figure out what was the issue?

[sreejithqb]

Yes Simon. That was an issue with Angle theme caching. Resolved the issue.
Thanks for your help. I am closing this issue