Skip to content

fix(venn): avoid broken fmin package-root exports - #3894

Open
dajiaohuang wants to merge 1 commit into
antvis:masterfrom
dajiaohuang:fix/venn-fmin-import-compat
Open

dajiaohuang wants to merge 1 commit into
antvis:masterfrom
dajiaohuang:fix/venn-fmin-import-compat

Conversation

@dajiaohuang

Copy link
Copy Markdown

Need

Restore Venn layout imports in the docs bundle and CommonJS build.

Updating reason

fmin@0.0.4 points its package root at a UMD file that exposes no named exports to the docs bundler. The existing Venn import also produced an unusable CommonJS layout at runtime. Replace that import with the small helper subset Venn needs, retain the upstream BSD license notice, and cover overlap bisection plus constrained layout with deterministic synthetic data. Related prior report: closed, unmerged PR #3888.

Related testing

  • Targeted Venn Jest tests: 2 suites, 4 tests passed.
  • npm run lint: passed; four pre-existing unused-variable warnings remain in unrelated tests.
  • npm run build: passed.
  • Synthetic compiled CommonJS Venn layout invocation: passed.
  • cd site && npm run build on Windows no longer reports the fmin named-export errors; Dumi then fails creating dist/:language/examples because : is invalid in Windows paths. No deployment or CI status was queried.

User tips

No public API or chart output format changed.

fmin@0.0.4's package root resolves to a UMD entry without named exports, breaking Venn layout builds and CommonJS execution. Keep the required helper subset local with its BSD attribution and cover the synthetic overlap and constrained-layout paths. Related: closed, unmerged PR antvis#3888.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant