Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 34 additions & 24 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions pnpm-workspace.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -52,11 +52,11 @@ catalog:
'@opentelemetry/resources': ^2.5.0
'@opentelemetry/sdk-node': ^0.217.0
'@playwright/test': 1.63.0
'@sveltejs/adapter-auto': ^7.0.1
'@sveltejs/adapter-auto': ^8.0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Keep adapter-auto compatible with the installed SvelteKit major · compatibility

For the orchestration UI, this pairs adapter-auto 8.0.1 with SvelteKit 2.70.3: packages/yucca-sdk/orchestration-ui/package.json:52–53 consumes both catalog entries, and its svelte.config.js:1–9 instantiates this adapter. Upstream 8.0.0 explicitly requires Kit 3, and 8.0.1 declares the peer range ^3.0.0-next.0; the catalog still requires Kit 2. Strict peer-dependency installations therefore reject this dependency graph. The generated lockfile retaining Kit 2 does not satisfy that contract.

Suggested fix

Keep adapter-auto at ^7.0.1 and regenerate pnpm-lock.yaml until SvelteKit is migrated to version 3 in a coordinated update.

Prompt for a coding agent
In pnpm-workspace.yaml line 55, restore @sveltejs/adapter-auto to ^7.0.1 while @sveltejs/kit remains ^2.70.3. Regenerate pnpm-lock.yaml so orchestration-ui resolves adapter-auto 7.0.1 with Kit 2.

'@sveltejs/adapter-node': ^5.5.7
'@sveltejs/adapter-static': ^3.0.10
'@sveltejs/kit': ^2.70.3
'@sveltejs/package': ^2.5.8
'@sveltejs/package': ^3.0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P0 Preserve $lib rewriting before upgrading svelte-package · compatibility

When packages/yucca-sdk/orchestration-ui/package.json:12 runs prepack, package 3.0.2 no longer injects the default $lib alias: its normalize_options only copies top-level config.alias and package imports. The new load-config loader receives Kit 2.70.3's svelte_config from the Vite plugin, with Kit options nested under kit, and the UI configuration supplies no top-level alias. Consequently imports such as $lib/options and $lib/services/backend.service in src/lib/components/backends/BackendsList.svelte:3–9 remain in the distributed components instead of becoming relative imports. The consuming web application then resolves these against its own $lib, breaking its build; its dependency on this library is at packages/web/package.json:40. This is a concrete packaging incompatibility beyond the advertised Node requirement.

Suggested fix

Retain @sveltejs/package ^2.5.8 and regenerate the lockfile until the packaging configuration is migrated and a packaged-output check confirms that library-internal $lib imports are rewritten to relative paths.

Prompt for a coding agent
Restore @sveltejs/package to ^2.5.8 in pnpm-workspace.yaml line 59 and regenerate pnpm-lock.yaml. Defer package 3 until the orchestration-ui configuration supplies aliases in the shape consumed by package 3. Add a regression check that prepack rewrites $lib/options and $lib/services/backend.service in distributed components to relative imports, and verify the web consumer builds against that output.

'@sveltejs/vite-plugin-svelte': ^7.3.1
'@tailwindcss/vite': ^4.1.18
'@tanstack/svelte-query': ^6.3.1
Expand Down
Loading