Leave Xylo

Eject copies the product into your repo so you no longer depend on Xylo’s private packages. It is the honest answer to “what if we leave.”

Caution. This is one-way. After eject you get no updates, no warranty, and no help from Xylo. It needs a clean git tree. Commit what it leaves. Do not run this because you are curious. Back up the repo and the database first.

Who should do this

Only the owner, with their agent, after a clear decision to stop taking Xylo updates.

What the command does

In the business repo (not the demo app):

pnpm xylo eject --yes

It:

1. Runs pnpm xylo sync so generated files match the installed core
2. Copies core into the repo (routes, library, components, tests)
3. Rewrites imports so they no longer point at @xylo/core
4. Removes the package dependency and registry auth
5. Leaves a note at the top of README.md

It refuses to run without --yes, or if the working tree is dirty, or if a path it would copy is already your own file.

What you keep

Your site, your admin, your database, your Stripe account, your customers. The app still builds with pnpm install and no private registry.

What you lose

New features and fixes from Xylo. The pnpm xylo command. Help.

This is not a maintained path. If you only wanted a backup, use nightly backups instead.