Repository navigation
docs: add Deploy to Wasmer option - #744
Open
ayushfromwasmer wants to merge 1 commit into
Open
ayushfromwasmer wants to merge 1 commit into
ayushfromwasmer wants to merge 1 commit into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/distworkflow 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 checkandnpm run buildpass 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.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
mainandnode-staticwith 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.