I get the following message: Unable to apply item style: class MISSINGCLASSNAME undefined`. On top of that, in our case there is also a delay in the rendering of the node items icons that are applied using the existing className (in this case, classLC). This makes the NetChart practically unusable for us because of the combination of error message and rendering delay.

I understand that this might not strictly be a bug, but given that the node or link className values come from the dataset, I believe it is reasonable to assume that not all of those classNames are going to be used in the styling process through the style object. In our case, the className values coming from the dataset are dynamically generated based on a specific property of the corresponding entity represented by the node. This means that we cannot just add them all in the style object within the nodeClasses array. We might use one or more to style the nodes, but not necessarily all of them, as we do not even know in advance what they are.

It would be great to hear what your thoughts are on this. Would it be difficult to add a check in the source code to prevent the error message and consequent rendering delay when there is not a corresponding className in the style object compared to the one in the data source?

I am replying here as well as I did not hear back from the email support. Maybe you can help me?

The example based on the new library version looks great! Is it possible to get this version released on NPM? That is how we get the ZoomCharts library, so unless it is available there we won’t be able to update our current version.

Thank you, however that solution does not work in our case, because of our architecture and how we initialise the library. We were planning on releasing our implementation of the library before the end of the week, any chance to have the NPM version updated either today or tomorrow? Let me know, thank you.

I see, thank you for the reply. Would it be possible to have some sort of time frame for the NPM update? This would help us a lot in identifying the best alternative strategy to access the latest version of the library while we wait for the NPM release and still deploy our implementation. Thank you!