Webstudio Fixtures

Fixtures are test projects that ensure the CLI and build process work correctly across different deployment targets.

Updating Fixtures After Changes

# From repository root - updates all fixtures
pnpm fixtures

This command will:

Link all fixtures to their respective projects
Sync the latest data from the development environment
Build all fixtures with the latest code

Working with Individual Fixtures

# Go to fixture folder
cd fixtures/webstudio-features

# Link to project
pnpm fixtures:link

# Sync latest data
pnpm fixtures:sync

# Build fixture
pnpm fixtures:build

# Start it
pnpm run dev

Adding Assets to Fixtures

To add a new asset (image, video, audio, etc.) to a fixture:

Publish to staging
- Make your changes in the builder
- Publish to the staging environment
Get the build ID from CI
- After publishing, check the CI logs
- Find the build ID that was created
Update the fixture's build ID
- Edit fixtures/[fixture-name]/package.json
- Update the --buildId parameter in the fixtures:sync script
```
"fixtures:sync": "pnpm cli sync --buildId NEW_BUILD_ID_HERE && pnpm oxfmt ./.webstudio/"
```

Sync with the correct environment

# Go to fixture folder
cd fixtures/webstudio-features

# Sync from staging environment (replace with your branch)
BUILDER_HOST=fix-assets.staging.webstudio.is pnpm run fixtures

Fix the origin URL
- After syncing, edit .webstudio/data.json
- Change the origin back to:
```
"origin": "https://main.development.webstudio.is"
```
- This is necessary because sync changes it to the current branch

Commit the changes

git add fixtures/
git commit -m "chore: update fixtures with new assets"
git push