DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to run public runtime tests before changing the runtime with Pixelcrabs

Run the dependency-free public runtime test suite to confirm a clean baseline before editing the local runtime.

Who it is forA contributor who plans to modify the local Web runtime or preview gateway and wants a known-good baseline first.

The problemChanges to the preview runtime are hard to judge without knowing whether the existing public tests pass on the machine.

The outcomeThe five public runtime test files run and report a result, giving a baseline before any edits.

What you need first

  • A computer with Node.js 24 or later installed
  • Bun 1.3.14 installed, for the pinned OpenCode engine
  • A local copy of the johnzhaors-bit/pixelcrabs repository
  • A static site folder containing index.html, or a project directory to point OpenCode at

Steps

  1. Confirm Node.js 24 or later is installed and open a terminal in the repository root.
  2. Run node --test packages/local-runtime/test/public-preview-core.test.mjs packages/local-runtime/test/public-static-preview.test.mjs packages/local-runtime/test/public-web-project.test.mjs packages/local-runtime/test/public-web-runtime.test.mjs packages/local-runtime/test/public-preview-gateway.test.mjs (inferred, check the README)
  3. Review the test output and note any failures before editing.
  4. Read .github/workflows/opencode-smoke.yml for the broader locked-dependency build and test sequence.

Prompt for your agent

In the pixelcrabs repository root, run the five public runtime test files with `node --test` as listed in the README. Expected output: a pass or fail summary for each test file. Verify that no test requires installed packages before reporting a baseline.

Caveat. The README says these five tests are dependency-free, but the broader CI workflow may download packages and need a native compiler toolchain.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page