0 Fork 0

mirror of https://github.com/webstudio-is/webstudio.git synced 2026-11-09 14:03:33 +09:00

Files

T

Oleg Isonen 82c3d83fd1 fix: optimize CLI import for large data amount (#5831 )

## Summary

- Add CLI project import support from synced `.webstudio/data.json` into
another project via a destination share link.
- Move project bundle import/export contract into
`@webstudio-is/protocol`, including bundle versioning, staged upload
constants, schema validation, and fixture coverage.
- Upload project bundle data through staged TUS upload before calling
the import RPC to avoid request body limits.
- Upload referenced assets as binary files through the existing asset
upload route before importing asset rows.
- Add `--skip-assets` and `--ignore-version-check` import options.
- Add retry handling for transient missing imported asset files by
re-uploading only the reported missing assets.
- Share missing-asset import error formatting/parsing through protocol
to avoid duplicated string contracts.
- Preserve browser asset upload behavior while adding API upload
support.
- Normalize schema naming across the branch to lower-case names without
`Schema` suffix.

2026-06-23 18:50:01 +02:00

react-router-cloudflare

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

react-router-docker

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

react-router-netlify

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

react-router-vercel

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

ssg-cloudflare-pages

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

ssg-netlify-by-project-id

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

webstudio-cloudflare-template

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

webstudio-features

fix: optimize CLI import for large data amount (#5831 )

2026-06-23 18:50:01 +02:00

README.md

fix: Fix asset resource on published sites (#5565 )

2026-01-15 18:26:32 +01:00

README.md

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 prettier --write ./.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