Latest version v5.2.1 breaks new assignment

[radames]

Not sure if the news pushes to static from 778acc9 were supposed to cause this error.

But now many d3-delaunay@5 are broken now if the initializaiont is done with new assignments
Was it an expected result? shall we move to

const delaunay = d3.Delaunay.from(particles);

instead of ?

const delaunay = new d3.Delaunay.from(particles);

Broken examples:
https://observablehq.com/@d3/hover-voronoi
https://observablehq.com/@fil/mobility-landscapes

[mourner]

I think the error is expected — you should only use new in combination with classes (new d3.Delaunay.from is incorrect), while from is a factory function that does instantiation internally.

[Fil]

Thanks for the links to the broken examples (in my garden :^) ). I agree that those examples are wrong — let's hope there are not too many of them in the wild.

…

-- Fil

[radames]

wonderful! thanks for the response, I've already fix some of my projects using the old new assignment. If I come across other notebooks on observables I'll send comments! Shall I close this issue?

[Fil]

unfortunately we can't search observable for "new d3.Delaunay.from"

[radames]

unfortunately we can't search observable for "new d3.Delaunay.from"

I've tried the quoted search, unfortunately it doesn't do the full matching search :(