Skip to content

docs: add Deploy to Wasmer option - #744

Open
ayushfromwasmer wants to merge 1 commit into
arthelokyo:mainfrom
ayushfromwasmer:docs/deploy-to-wasmer
Open

ayushfromwasmer wants to merge 1 commit into
arthelokyo:mainfrom
ayushfromwasmer:docs/deploy-to-wasmer

Conversation

@ayushfromwasmer

@ayushfromwasmer ayushfromwasmer commented Oct 22, 2026 •

Copy link
Copy Markdown

Deploy to Wasmer

Review the repository, branch and build settings in Wasmer before clicking Deploy.

I work at Wasmer. Wasmer Edge can serve AstroWind's generated static website using its WebAssembly runtime.

Adds a deployment badge and six README lines beside the existing hosting options. People adapting the template for their own business or blog can publish an owned fork and update it through Git. The text names the existing npm run build/dist workflow and explains importing a fork for custom content. No application code, build configuration or dependencies change. This contribution was prepared and reviewed with AI assistance.

Testing

At exact head deb589391de4e2366a5cc4a6c0ebd52f545f06e8:

  • npm ci, npm run check and npm run build pass on Windows with Node24.22.1/npm11.19.1. Astro checks108 files with zero errors/warnings/hints; ESLint and Prettier pass. The production build reports39 pages,36 optimized images and one copied font. Source and lockfile remain unchanged.
  • Claude independently checks homepage, blog, a post, dark mode and the390x844 mobile menu on the development server. These views render with no page JavaScript errors; intentionally blocked external resources produce console/network errors. These are dev-server views, not production-browser proof.
  • Claude's Anybuild0.33.0 plan selects Astro/static Node.js and dist. Its replay build is blocked by that environment's Fontsource/Pixabay egress restrictions; the separate Windows production build above succeeds with the original asset-fetch behavior.

The live Wasmer import page selects main and node-static with Deploy enabled. No deployment was submitted.

The install reports16 dependency findings (five moderate, eleven high); this documentation change does not remediate them. Builds require access to their configured font/image sources. Existing template URLs, branding and configuration still need personalization in a fork.

No hosted deployment, WASI serving or production-output browser check has been verified in this refresh. The button opens import configuration and creates no GitHub copy.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant