vite-plugin-zephyr 1.4.2 → 1.5.0

package/skills/zephyr-core/references/sdk-setup.md

@@ -0,0 +1,166 @@
+# SDK Setup
+
+Use this file when the user asks how to add Zephyr to a frontend project, which SDK/plugin to install, or whether `with-zephyr` can wire up an existing app.
+
+## Fastest path
+
+For an existing app, start with the codemod:
+
+```bash
+curl -fsSL https://with.zephyr-cloud.io | node
+```
+
+Other launch forms:
+
+```bash
+npx with-zephyr
+yarn dlx with-zephyr
+pnpx with-zephyr
+bunx with-zephyr
+```
+
+Why: the codemod detects the stack and makes the smallest setup change for supported bundlers/frameworks.
+
+## Minimal prerequisites
+
+- A Zephyr account or org/app access path
+- A git repository with a remote, branch, and commit
+- A supported Zephyr SDK path, or a build output directory for `zephyr-agent`
+
+## What happens after `with-zephyr`
+
+- It detects the stack and usually adds the matching Zephyr integration to the project config.
+- It may add or update the relevant build config file for the bundler/framework.
+- The next step is normally just to run the app's build command.
+- After a successful Zephyr-enabled build, look for the version URL in the build output/logs.
+
+## SDK picker
+
+Use the official picker doc first:
+
+- Docs page: `https://docs.zephyr-cloud.io/getting-started/find-your-sdk`
+- Raw markdown: `https://docs.zephyr-cloud.io/getting-started/find-your-sdk.md`
+- Source: `https://docs.zephyr-cloud.io/getting-started/find-your-sdk.md`
+
+Current mapping:
+
+| Stack             | SDK                                 |
+| ----------------- | ----------------------------------- |
+| Vite              | `vite-plugin-zephyr`                |
+| Webpack           | `zephyr-webpack-plugin`             |
+| Rspack            | `zephyr-rspack-plugin`              |
+| Rsbuild / Rslib   | `zephyr-rsbuild-plugin`             |
+| Rollup            | `rollup-plugin-zephyr`              |
+| Rolldown          | `zephyr-rolldown-plugin`            |
+| Parcel            | `parcel-reporter-zephyr`            |
+| Metro             | `zephyr-metro-plugin`               |
+| Re.Pack           | `zephyr-repack-plugin`              |
+| Astro             | `zephyr-astro-integration`          |
+| Modern.js         | `zephyr-modernjs-plugin`            |
+| Nitro v3          | built-in `preset: 'zephyr'`         |
+| Nuxt              | `zephyr-nuxt-module`                |
+| Rspress           | `zephyr-rspress-plugin`             |
+| Ember.js via Vite | `vite-plugin-zephyr`                |
+| TanStack Start    | `vite-plugin-tanstack-start-zephyr` |
+| Vinext            | `vite-plugin-vinext-zephyr`         |
+
+Fallback for unsupported stacks:
+
+```ts
+import { uploadOutputToZephyr } from 'zephyr-agent';
+
+await uploadOutputToZephyr({
+  rootDir: process.cwd(),
+  outputDir: '.output',
+  ssr: true,
+});
+```
+
+For a build command or prebuilt directory without a bundler integration, the
+`zephyr-cli` package wraps the command and uploads its output:
+
+```bash
+ze-cli pnpm build
+ze-cli deploy ./dist
+```
+
+Use these fallbacks when there is no official Zephyr SDK for the stack, but the project still produces a deployable output directory. They are the low-level integration paths for custom frameworks and internal tooling.
+
+Minimum assumption: Zephyr still needs a real built output directory and enough app/build context to upload it correctly.
+
+## Smallest working examples
+
+Vite:
+
+```ts
+import { defineConfig } from 'vite';
+import react from '@vitejs/plugin-react';
+import { withZephyr } from 'vite-plugin-zephyr';
+
+export default defineConfig({
+  plugins: [react(), withZephyr()],
+});
+```
+
+Source example: `https://github.com/ZephyrCloudIO/zephyr-examples/blob/main/bundlers/react-vite/vite.config.ts`
+
+Rspack:
+
+```ts
+import { defineConfig } from '@rspack/cli';
+import { withZephyr } from 'zephyr-rspack-plugin';
+
+const config = defineConfig({
+  entry: { main: './src/main.tsx' },
+});
+
+export default withZephyr()(config);
+```
+
+Source example: `https://github.com/ZephyrCloudIO/zephyr-examples/blob/main/bundlers/react-rspack/rspack.config.ts`
+
+TanStack Start:
+
+```ts
+import { withZephyr } from 'vite-plugin-tanstack-start-zephyr';
+
+plugins: [tanstackStart(), viteReact(), withZephyr()];
+```
+
+Source example: `https://github.com/ZephyrCloudIO/zephyr-examples/blob/main/frameworks/tanstack-start/vite.config.ts`
+
+Astro:
+
+```js
+import { defineConfig } from 'astro/config';
+import { withZephyr } from 'zephyr-astro-integration';
+
+export default defineConfig({
+  integrations: [mdx(), sitemap(), withZephyr()],
+});
+```
+
+Source example: `https://github.com/ZephyrCloudIO/zephyr-examples/blob/main/frameworks/astro/astro.config.mjs`
+
+## Important setup notes
+
+- Plugin placement is stack-specific, not globally “always last”.
+- Nx compose-plugin setups usually put Zephyr last in the composition.
+- Vite Module Federation and framework-specific integrations can require a specific order; verify against the stack docs/example before moving plugins around.
+- For existing apps, prefer the codemod before hand-editing configs.
+- Git context matters for deployment identity: repo, branch, and commit need to exist.
+- If docs disagree on Rspack naming, prefer `zephyr-rspack-plugin` from the SDK picker and examples.
+
+## Important availability caveats
+
+- Astro integration is static-only. Do not present it as a general SSR deployment path.
+- Nitro v3, Nuxt, and TanStack Start SSR-style paths are currently constrained to Zephyr's managed Cloudflare path in the public docs.
+- If the user needs unsupported SSR behavior or a custom runtime, verify whether `zephyr-agent` output upload is a better fit than an official framework SDK.
+
+## Best docs to link
+
+- Quick start: `https://docs.zephyr-cloud.io/getting-started/quick-start.md`
+- SDK picker: `https://docs.zephyr-cloud.io/getting-started/find-your-sdk.md`
+- Existing app integration: `https://docs.zephyr-cloud.io/integrations/existing-app.md`
+- Vite: `https://docs.zephyr-cloud.io/bundlers/vite.md`
+- llms index: `https://docs.zephyr-cloud.io/llms.txt`

package/skills/zephyr-core/references/troubleshooting.md

@@ -0,0 +1,48 @@
+# Troubleshooting
+
+Use this file for common Zephyr setup and build failures.
+
+## First checks
+
+- Confirm the stack is using the right SDK/plugin.
+- Confirm the project is a git repo with a remote, branch, and commit.
+- Confirm the user is authenticated and has access to the target app/org.
+- Confirm the Zephyr integration is attached to the actual build config being executed.
+
+## Common failure classes
+
+### Wrong plugin for the stack
+
+- Vite -> `vite-plugin-zephyr`
+- Rspack -> `zephyr-rspack-plugin`
+- Webpack -> `zephyr-webpack-plugin`
+- TanStack Start, Vinext, Astro, Rspress, Nuxt, Nitro -> prefer their dedicated integration paths
+
+### Git context missing
+
+Common symptoms:
+
+- app identity cannot be resolved
+- build ID / auth / application UID errors
+- deployment metadata is incomplete
+
+### Auth/access mismatch
+
+Common symptoms:
+
+- login succeeds locally but deploy cannot write
+- CI token works for one org/app but not another
+- build accepts config but publish fails later
+
+### Docs drift to call out
+
+- If Rspack docs and examples disagree, prefer `zephyr-rspack-plugin` from the SDK picker and examples.
+- Public docs around status names have some drift; keep answers focused on immutable versions plus mutable routing targets.
+
+## Good error docs
+
+- Error index: `https://docs.zephyr-cloud.io/errors.md`
+- Git remote missing: `https://docs.zephyr-cloud.io/errors/ze10014.md`
+- Git config missing: `https://docs.zephyr-cloud.io/errors/ze10016.md`
+- Auth error: `https://docs.zephyr-cloud.io/errors/ze10018.md`
+- Build ID failure: `https://docs.zephyr-cloud.io/errors/ze10019.md`

package/skills/zephyr-module-federation/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026-present Zephyr Cloud and contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/skills/zephyr-module-federation/README.md

@@ -0,0 +1,12 @@
+# zephyr-module-federation
+
+Skill for Zephyr Module Federation setup and remote resolution workflows.
+
+Includes:
+
+- `SKILL.md` for the main trigger and workflow
+- `references/setup-patterns.md` for host/remote config patterns
+- `references/remote-resolution.md` for `zephyr:dependencies` and selector behavior
+- `references/examples.md` for working example paths
+- `references/gotchas.md` for common MF issues
+- `references/docs-map.md` for deeper docs links

package/skills/zephyr-module-federation/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: zephyr-module-federation
+description: Use when the user asks about zephyr:dependencies, hosts/remotes, Module Federation build order, remote resolution, cross-bundler remotes, or monorepo MF on Zephyr.
+license: Apache-2.0
+metadata:
+  author: Zephyr Cloud IO
+  purpose: Use when the user asks about zephyr:dependencies, hosts/remotes, Module Federation build order, remote resolution, cross-bundler remotes, or monorepo MF on Zephyr.
+  domain: federation
+  type: core
+sources:
+  - ZephyrCloudIO/zephyr-packages:**/skills/zephyr-module-federation/references/*.md
+  - ZephyrCloudIO/zephyr-packages:**/scripts/sync-package-skills.mjs
+---
+
+# Zephyr Module Federation
+
+Use this skill for Zephyr's Module Federation workflow: host/remote setup, `zephyr:dependencies`, resolution behavior, build order, and cross-bundler examples.
+
+Module Federation is the pattern where a host app loads code from separately built remote apps at runtime.
+
+Zephyr does not replace normal Module Federation config; it adds deploy-time dependency resolution and routing on top of the host/remote setup.
+
+Use this skill when the user needs help wiring, resolving, or deploying hosts/remotes. Use `zephyr-core` when the question is mostly about general Zephyr setup, version URLs, tags/environments, or public env vars.
+
+## What to cover
+
+- Explain both layers: bundler MF config and Zephyr dependency mapping.
+- Prefer concrete examples over abstract theory.
+- Keep the answer grounded in the user's stack: Webpack, Rspack, Vite, Rsbuild, Turbo, Nx, or mixed-bundler.
+- If the question is mostly about general Zephyr setup, version URLs, tags/envs, or public env vars, also read `../zephyr-core/SKILL.md`.
+- Localhost remote URLs in examples are for local development only; deployed answers should steer toward Zephyr resolution instead of hardcoded production URLs.
+
+## Core mental model
+
+- Module Federation defines host/remote wiring in bundler config.
+- Zephyr adds deploy-time dependency resolution through `zephyr:dependencies`.
+- `workspace:*` is the most important Zephyr-specific dev workflow for coordinated branch/user/CI resolution.
+- Remotes usually need to be built before hosts.
+- Names must stay consistent across `package.json`, MF config, and dependency declarations.
+
+## Answer flow
+
+1. Read `references/setup-patterns.md` for host/remote config shapes.
+2. Read `references/remote-resolution.md` for `zephyr:dependencies`, selectors, and `workspace:*`.
+3. Read `references/examples.md` for concrete file paths and snippets.
+4. Read `references/gotchas.md` for build order, naming, and mixed-bundler edge cases.
+5. Link deeper docs from `references/docs-map.md`.
+
+## Source priorities
+
+- Public docs source: `https://docs.zephyr-cloud.io`
+- Examples source: `https://github.com/ZephyrCloudIO/zephyr-examples`
+- Docs site: `https://docs.zephyr-cloud.io`
+- Raw docs path pattern: `https://docs.zephyr-cloud.io/<path>.md`
+- Docs index: `https://docs.zephyr-cloud.io/llms.txt`
+
+## Guardrails
+
+- Do not treat `zephyr:dependencies` as a replacement for MF config; it complements it.
+- Do not recommend hardcoded production remote URLs when Zephyr resolution should be used.
+- Do not ignore build order for remotes and hosts.
+- Call out naming mismatches early; they are a common failure source.

package/skills/zephyr-module-federation/references/docs-map.md

@@ -0,0 +1,10 @@
+# Docs Map
+
+## Best first links
+
+- MF guide: `https://docs.zephyr-cloud.io/tutorials/mf-guide.md`
+- Remote dependencies: `https://docs.zephyr-cloud.io/features/remote-dependencies.md`
+- Multi-bundler integration: `https://docs.zephyr-cloud.io/integrations/vite-rspack-webpack-mf.md`
+- Versions: `https://docs.zephyr-cloud.io/features/versions.md`
+- Tags & environments: `https://docs.zephyr-cloud.io/features/tags-environments.md`
+- Docs index: `https://docs.zephyr-cloud.io/llms.txt`

package/skills/zephyr-module-federation/references/examples.md

@@ -0,0 +1,33 @@
+# Examples
+
+Use this file when the user wants concrete working MF examples to copy from.
+
+## Best examples
+
+- Webpack host/remote: `https://github.com/ZephyrCloudIO/zephyr-examples/tree/main/module-federation/react-webpack`
+- Rsbuild consumer/provider: `https://github.com/ZephyrCloudIO/zephyr-examples/tree/main/module-federation/react-rsbuild`
+- Cross-bundler host + remotes: `https://github.com/ZephyrCloudIO/zephyr-examples/tree/main/module-federation/react-vite-rspack-webpack`
+- Advanced staged builds: `https://github.com/ZephyrCloudIO/zephyr-examples/tree/main/module-federation/tractor-sample`
+- Turborepo monorepo MF: `https://github.com/ZephyrCloudIO/zephyr-examples/tree/main/build-systems/turborepo-rspack-mf`
+
+## Strong snippets
+
+### Cross-bundler Vite host
+
+File: `https://github.com/ZephyrCloudIO/zephyr-examples/blob/main/module-federation/react-vite-rspack-webpack/host/vite.config.ts`
+
+- Good for showing remote `type: 'module'` vs `type: 'var'`
+- Good for showing `withZephyr({ mfConfig })`
+
+### Host dependency mapping
+
+File: `https://github.com/ZephyrCloudIO/zephyr-examples/blob/main/module-federation/react-vite-rspack-webpack/host/package.json`
+
+- Good for `workspace:*` mapping
+
+### Turborepo build-order explanation
+
+File: `https://github.com/ZephyrCloudIO/zephyr-examples/blob/main/build-systems/turborepo-rspack-mf/README.md`
+
+- Good for explaining why remotes should build before host
+- Good for monorepo orchestration answers

package/skills/zephyr-module-federation/references/gotchas.md

@@ -0,0 +1,54 @@
+# Gotchas
+
+Use this file when the user is stuck or their MF setup looks valid but still fails.
+
+## Common issues
+
+### Remotes built after host
+
+- Zephyr usually needs remotes available first to resolve them cleanly.
+- In cyclic setups, users may need a staged build process.
+
+### Naming mismatch
+
+Keep names aligned across:
+
+- remote `package.json` `name`
+- MF config `name`
+- host remotes keys / import names
+- `zephyr:dependencies` keys and targets
+
+If these drift, resolution and runtime loading become fragile fast.
+
+### Mixed-bundler remote type mismatch
+
+- Vite module remotes often use `type: 'module'`
+- Webpack/Rspack-style remotes may use `type: 'var'`
+- If the user picks the wrong type, the host may fail to load the remote at runtime even if the deploy succeeded.
+
+### Vite-specific MF caveats
+
+- Plugin order can matter in Vite MF setups; do not assume Zephyr should always be the last plugin.
+- `build.target` may need to account for top-level await support in MF setups.
+- `modulePreload` behavior can matter for cross-bundler Vite setups.
+- Use the Zephyr Vite MF docs/examples when debugging these issues rather than generic plugin-order guesses.
+
+### Hardcoded URLs left in place
+
+- Hardcoded localhost URLs are fine for local example configs.
+- For Zephyr answers, steer the user toward Zephyr dependency resolution rather than manually swapping production remote URLs.
+
+### Git and access still matter
+
+- MF setup can be correct while deployment still fails because git context or app access is missing.
+
+### Missing remote build
+
+- `workspace:*` falls back to the latest published version of the remote when no matching workspace build exists, so it still fails if the remote has never been published.
+- If resolution fails, check that the remote was built and published first. Other selectors have no such fallback and need a matching tag, environment, or version.
+
+## Quick diagnostic flow
+
+1. If the host cannot find the remote at all, check naming alignment first.
+2. If naming is correct but Zephyr cannot resolve the remote target, check selector choice and whether the remote was built into a resolvable environment.
+3. If resolution succeeds but runtime loading still breaks, check remote `type`, Vite MF caveats, and bundler compatibility.