Bumps the testing-deps group with 4 updates in the / directory: [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8), [@vitest/ui](https://github.com/vitest-dev/vitest/tree/HEAD/packages/ui), [jsdom](https://github.com/jsdom/jsdom) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `@vitest/coverage-v8` from 5.0.3 to 5.0.5 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/coverage-v8) Updates `@vitest/ui` from 5.0.3 to 5.0.5 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/ui) Updates `jsdom` from 30.0.1 to 30.1.3 - [Release notes](https://github.com/jsdom/jsdom/releases) - [Commits](https://github.com/jsdom/jsdom/compare/v30.0.1...v30.1.3) Updates `vitest` from 5.0.3 to 5.0.5 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.5/packages/vitest) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 5.0.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing-deps - dependency-name: "@vitest/ui" dependency-version: 5.0.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing-deps - dependency-name: jsdom dependency-version: 30.1.3 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: testing-deps - dependency-name: vitest dependency-version: 5.0.5 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: testing-deps ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Lucide Solid 2 integrations
These fixtures exercise the built @lucide/solid package in a real Solid 2 (release candidate) consumer app.
The vite fixture was scaffolded with the Solid 2.0 basic template:
npm create solid@latest -- --solid -t basic --ts
It keeps the template's turnkey client mode (@solidjs/vite-plugin with start: true, filesystem-routing and @solidjs/router), with the demo pages replaced by the icon showcase. The template's tooling versions are aligned with the workspace: TypeScript 6 and the workspace's pinned Vitest 4.
There is no SolidStart fixture yet, because SolidStart still targets Solid 1. The Solid 1 fixtures for lucide-solid live in ../lucide-solid.
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-2-vite exec playwright install chromium
pnpm test:integrations:solid-2
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.
tsconfig.declarations.json compiles only src/IconShowcase.tsx (the file that imports the public entry points) with skipLibCheck: false and no ambient types. This makes tsc read the declarations shipped in dist/types, so a .d.ts that points at a file the build never emitted fails the check. Both run under pnpm typecheck.
file-routes.d.ts is generated by filesystem-routing on every build and is committed so tsc can resolve virtual:file-routes before a build has run.