Module "delaunator" not found. Only listed as devDependency.

[tannerlinsley]

Not sure if this is intended, but it looks like "delaunator" might need to be added as a production dependency to not get this error.

[mourner]

This is intended, because delaunator gets inlined for the release as a build step. https://github.com/d3/d3-delaunay/blob/master/package.json#L36

[tannerlinsley]

When installing with Yarn, I got a webpack bundling error that it could not be found. Any other reason that this might happen?

…

On Mon, Apr 9, 2018 at 9:29 AM Vladimir Agafonkin ***@***.***> wrote: This is intended, because delaunator gets inlined for the release as a build step. https://github.com/d3/d3-delaunay/blob/master/package.json#L36 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#35 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFUmCV_xR_RsN2byqqUJx9dHS-z9PlO3ks5tm34zgaJpZM4TMuri> .

[tannerlinsley]

I think what's happening is that since the package.json module definition points to the source, it is hitting the import delaunator from 'delaunator', and throwing this error. I wonder, should the the module definition be removed, point to a dist, or the dependency moved to production?

[mourner]

Oh, you're right. I forgot about the module entry point. We should move the dependency to production then.

[mbostock]

I think my eventual plan is for the module entry point to point to a minified Rollup ES module, so that when you load d3-delaunay from unpkg it only triggers a single request. But adding this as a production dependency for now would be fine. 👍