You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for reporting this. This relates to a corresponding issue with npm-force-resolutions here rogeriochaves/npm-force-resolutions#10 - I'll see if I can come up with a workaround.
This seems to be the real issue: package-lock.json doesn't get published to npm, that's why the preinstall script will not find it: rogeriochaves/npm-force-resolutions#12
I can confirm that install breaks and package-lock.json isn't generated when I include d3-milestones in package.json. Installation completes when I disable scripts (npm install --ignore-scripts) since it disables the preinstall script. Packages won't work as expected though since some scripts are needed. But this may help zero-in on the root cause in code.
I updated the build setup to no longer make use of npm-force-resolutions, it caused too much trouble with that preinstall issue. Just released v1.0.1 which should install without the error.
The text was updated successfully, but these errors were encountered: