Point package metadata at figma/ and refresh dependencies - #41
Open
toeknee-figma wants to merge 1 commit into
Open
Point package metadata at figma/ and refresh dependencies#41toeknee-figma wants to merge 1 commit into
toeknee-figma wants to merge 1 commit into
Conversation
The npm package still advertised the Modyfi organisation, whose repository is now empty, so anyone following the package page landed nowhere (#40). js-yaml moves to ^4.3.1, which carries the fix for GHSA-mh29-5h37-fv8m (#38). Caret ranges replace exact pins on the runtime dependencies so downstream installs can dedupe and pick up patches without a release here. Type resolution for CommonJS consumers was falling back to the ESM declarations; the export conditions now name index.d.cts for require and index.d.ts for import. Also drops c8, which no script invoked, and gives example/ its own vite pin so the integration build exercises a version near the bottom of the supported peerDependencies range rather than the one the plugin is built against. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Aug 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First of three stacked PRs sorting out the repo. This one is metadata and dependencies only — no behaviour changes — so it can merge on its own.
Metadata
repository,bugsandhomepagestill pointed at the Modyfi organisation, whose repository is now empty, so the npm package page led nowhere. Fixes #40.This only reaches users once the package is republished. npm owners are currently
tonyketchamandpiers-modyfi, with no Figma org, so that step needs someone holding those credentials.Dependencies
js-yaml→^4.3.1, carrying the fix for GHSA-mh29-5h37-fv8m. Fixes Upgrade js-yaml Dependency #38 and supersedes Upgrade js-yaml #39 — thanks @hstrowd, whose patch targeted 4.1.1; 4.3.1 is the current v4 line and a drop-in.c8dropped — no script ever invoked it.tsup,typescriptandvitebumped. Supersedes Bump vite from 5.0.13 to 5.4.19 #36.vitegoes to 7.x as the version the plugin is typed and built against, andexample/gets its own pin at 5.4.21 so the integration build keeps exercising a version near the bottom of the>=3.2.7range rather than the newest one.Type resolution
CommonJS consumers were resolving to the ESM declarations (
arethetypeswrongreported "Masquerading as ESM"). The export conditions now nameindex.d.ctsforrequireandindex.d.tsforimport; all four resolution modes come back clean.filesalso listed atypesdirectory that does not exist.Verification
pnpm typecheck,pnpm buildandpnpm example:buildall pass.🤖 Generated with Claude Code