Skip to main content

ARC 2.0.0-beta.25

Run, check, and inspect

Check, build, and directly run a local blocklet, then verify its Web Device page in a browser.

From the my-site/ directory created on the previous page, run:

bash
arc dsl lint .
arc dsl validate .
arc blocklet check .
arc blocklet build .

On 2.0.0-beta.25, the minimal site produced Passed DSL lint, Passed DSL validation, Passed blocklet check (basic), and build output in dist/. That output is local build material. Do not commit it unless your project’s publishing process explicitly requires it.

Run the current blocklet directly

bash
arc blocklet run .

ARC reuses or starts a local daemon and prints the actual URL for this blocklet. The port and host depend on your machine, so copy the reported URL rather than constructing one by hand.

Open the primary URL printed by your command. Do not substitute a host or port from another machine, an example, or an earlier run. You should see:

  • Hello, Web Device as the heading;
  • This page is rendered by a local blocklet. as the body text;
  • no horizontal overflow or browser console errors.

This browser check is the page acceptance step. DSL validation and build prove that the inputs can be processed; the browser proves what a reader will actually receive.

Start with the first failure

SymptomCheck first
missing_web_component_fileConfirm that manifest.json, render.js, and style.css live in the same custom-component directory.
The page says it has no direct app entryConfirm .route/web exists and that handler: web, source: ., and site are correct.
arc blocklet build failsFix the first error from arc dsl lint or arc dsl validate, then build again.
The URL does not openDo not deploy to DID Space. Check the exact host and port printed by the command, then check whether another local service already uses that port.

You have now verified a minimal static site. Add content next through Content objects, metadata, and locales, or use Reference when you need a particular field or syntax rule.