Issue with production build of react.

[adityamulik]

Please find the attached error in production build of ReactJS app. It works fine in dev server.

[dangreen]

@adityamulik Hi. Would you please provide minimal reproduction of the issue (repo, codesandbox, ...)?

[dangreen]

@adityamulik It seems like you are passing undefined to the data prop. data prop is required; it must be an object with a datasets array.

[santiacho]

I think the problem should be when the chart renders. If the render cycle didn't feed the data on time will crash. The same happened to me and I just fixed that controlling when the data is ready before rendering the Doughnut chart:

{chartData && (
    <Doughnut
      data={chartData}
      options={{
        plugins: {
          legend: {
            display: false,
          },
          title: {
            display: false,
          },
          tooltip: { enabled: false },
        },
        responsive: true,
        maintainAspectRatio: false,
      }}
    />
  )}

That solved my problem.

[dangreen]

@adityamulik @santiacho Hi. Please check out v4.0.0 with the new datasetIdKey prop.

[Dmitriy-Krivetsky]

@dangreen, hi i have a similar problem.

This problem only concerns the doughnut chart.
I tried

chart.js.       - 3.6.0 / 3.3.0 / 3.6.0
react-chartjs-2 - 3.3.0 / 3.3.0 / 4.0.0

it works on the test server, but I get an error in production. The difference in assembly scripts in

production: "build": "NODE_ENV=production webpack --mode production --progress", 
test: "new_test": "cross-env NODE_ENV=test webpack --mode production --progress",

[dangreen]

@Dmitriy-Krivetsky Hi. This is a different problem. It seems like minification is broken in your configuration.

[Dmitriy-Krivetsky]

@dangreen, thank you. Updating babel-eslint from 10.1 to 10.1.0 helped me

[dangreen]

@adityamulik Is this issue still relevant for you?

[adityamulik]

@dangreen Hi Dan, I seem to not have checked yet. I will cross check and confirm at the earliest. Thanks for your prompt support.

[adityamulik]

@dangreen Thanks, the issue is fixed. Updated my package.json file and all seems to be working.