Files
Eric FennisandClaude Opus 5.5 4b203ec9b6 chore(deps): Fix security vulnerabilities alerts (#5147)
* Upgrade deps

* Fix security alerts

* Keep incompatible consumers off minimatch 11 and file-type 21

The security overrides forced minimatch 11 and file-type 21 onto every
consumer, which broke ESLint (eslint-plugin-import-x imports the removed
makeRe) and the font build (jimp 0.22 calls file-type's removed
fromBuffer). glob 7 and @eslint/eslintrc also rely on the minimatch 3
callable export. Scope those consumers back to their compatible lines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Remove minimatch override

* Fix font build

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 20:58:02 +01:00
..

Lucide Solid integrations

These fixtures exercise the built lucide-solid package in real consumer frameworks.

Every fixture runs three checks:

  • a framework production build;
  • TypeScript with noEmit;
  • Vitest Browser Mode in Chromium.

From the repository root, install Chromium once and run the complete suite:

pnpm --filter @lucide/integration-solid-vite exec playwright install chromium
pnpm test:integrations:solid

The fixtures depend on lucide-solid through workspace:*, but import only its public package entry points. The root command builds lucide-solid before running any consumer checks.

Two TypeScript projects per fixture

tsconfig.json typechecks the fixture's own sources with skipLibCheck: true, like the React fixtures do, because the third-party declarations a Vite app pulls in are not clean under TypeScript 6.

tsconfig.declarations.json compiles only src/IconShowcase.tsx — the file that imports the public entry points — with skipLibCheck: false and no ambient types. That makes tsc read the declarations shipped in dist/types instead of skipping them, so a .d.ts that points at a file the build never emitted fails the check. Both run under pnpm typecheck.

Note that this does not reproduce the bug fixed in #4846, where the published declarations imported @lucide/shared/types: inside the workspace that specifier still resolves through packages/lucide-solid/node_modules. Catching that needs a check against the published tarball rather than the workspace link.