Lérè
2558b41d61
<!-- Thank you for contributing to Ruff/ty! To help us out with reviewing, please consider the following: - Does this pull request include a summary of the change? (See below.) - Does this pull request include a descriptive title? (Please prefix with `[ty]` for ty pull requests.) - Does this pull request include references to any relevant issues? - Does this PR follow our AI policy (https://github.com/astral-sh/.github/blob/main/AI_POLICY.md)? --> ## Summary <!-- What's the purpose of the change? What does it do, and why? --> - Adds some graceful degradation to Pyodide loading failures in the ty playground (with the result that the entire playground UI doesn't disappear if we only fail to execute a code run). - Corrects the placement of assets in our playground deployment, and adds some validation to the deployment workflow as a simple regression test Closes https://github.com/astral-sh/ty/issues/3409. ## Test Plan I've verified the new asset layout in a local build of the playground. I think that's sufficient, but I will monitor the production playground deployment and revert this change if necessary. <!-- How was it tested? -->
playground
In-browser playground for Ruff. Available https://play.ruff.rs/.
Getting started
Install the NPM dependencies with npm ci --ignore-scripts, and run the development server with
npm start --workspace ruff-playground or npm start --workspace ty-playground.
You may need to restart the server after making changes to Ruff or ty to re-build the WASM
module.
To run the datastore, which is based
on Workers KV,
install the Wrangler CLI,
then run npx wrangler dev --local from the ./playground/api directory. Note that the datastore
is
only required to generate shareable URLs for code snippets. The development datastore does not
require Cloudflare authentication or login, but in turn only persists data locally.
Architecture
The playground is implemented as a single-page React application powered by Vite, with the editor experience itself powered by Monaco.
The playground stores state in localStorage, but supports persisting code snippets to
a persistent datastore based
on Workers KV
and exposed via
a Cloudflare Worker.
The playground design is originally based on Tailwind Play, with additional inspiration from the Biome Playground.
Known issues
Stack overflows
If you see stack overflows in the playground, build the WASM module in release mode:
npm run --workspace ty-playground build:wasm.