mirabilos

unfortunately out of scope, but I hope I gave a helpful workaround

@laczko090 override how exactly? (I can reproduce the issue.)

Ouch. Agreed, but tricky.

Does it work if you do: import 'dygraphs'; import "dygraphs/src/extras/crosshair.js"; Unfortunately, I have no way to test this myself. Please provide a minimum working example where importing and using Dygraphs...

Sanket Rasal dixit: >The normal dygraph is working just fine. I am rendering large amount of data using it. Could you share a minimal Angular project in which it works...

I’ve now fixed this, using the following syntax… ``` import Dygraph from 'dygraphs'; import "dygraphs/src/extras/crosshair.js"; import 'dygraphs/src/extras/hairlines.js'; import 'dygraphs/src/extras/rebase.js'; import 'dygraphs/src/extras/shapes.js'; import 'dygraphs/src/extras/smooth-plotter.js'; import 'dygraphs/src/extras/super-annotations.js'; import 'dygraphs/src/extras/synchronizer.js'; import 'dygraphs/src/extras/unzoom.js'; ```...

Yes, see the import snippet above. Make sure to use the latest version.

Looks to me like something is pulling in an older version of dygraphs.

ng-dygraphs is pulling in dygraphs 2.1.0 for example.

Hmm, weird. When I add… ``` console.log(Dygraph.VERSION); console.log(Dygraph._require); ``` … then the correct things are output (`2.2.1` and `ƒ require()`, respectively). But when I enable one of the extras… ```...