Skip to content

feat(builder): adopt higher-level adapters-vite integration#376

Merged
pasevin merged 3 commits into
mainfrom
feat/adapters-vite-helper-adoption
Mar 29, 2026
Merged

feat(builder): adopt higher-level adapters-vite integration#376
pasevin merged 3 commits into
mainfrom
feat/adapters-vite-helper-adoption

Conversation

@pasevin

@pasevin pasevin commented Mar 29, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • switch the builder app over to the published @openzeppelin/adapters-vite helper API and add the shared adapter ecosystem mapping entry point
  • refresh builder dependency resolution and lockfile state against the published @openzeppelin/adapters-vite@^1.3.0 release
  • move the adapter architecture guide source of truth into openzeppelin-adapters and update builder docs/spec references accordingly

Test plan

  • pnpm install
  • pnpm --filter @openzeppelin/ui-builder-app typecheck
  • pnpm --filter @openzeppelin/ui-builder-app build

Align the builder app with the published adapters-vite helper package,
refresh the lockfile against the npm release, and keep the adapter extraction
follow-up changes bundled in the same consumer migration.
@pasevin
pasevin requested a review from a team as a code owner March 29, 2026 10:09
pasevin added 2 commits March 29, 2026 13:30
Order adapter subpath aliases ahead of the package root so Vitest resolves
`@openzeppelin/adapter-*/metadata` and `@openzeppelin/adapter-*/networks`
correctly during export and coverage test runs.
Remove the temporary Vitest export path override now that adapters-vite ships
the safe default alias order, and refresh the builder lockfile to the published
`@openzeppelin/adapters-vite@^1.3.1` release.
@pasevin
pasevin merged commit db2735e into main Mar 29, 2026
13 checks passed
@pasevin
pasevin deleted the feat/adapters-vite-helper-adoption branch March 29, 2026 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant