npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@craft-ts/deploy-alchemy

v0.8.8

Published

Optional Alchemy provider for CraftTS deployments: Cloudflare and AWS presets driven by the deployment manifest

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ronnainronnain

Keywords

craft-tsdeploymentalchemycloudflareawsinfrastructuretypescript

Readme

@craft-ts/deploy-alchemy

Optional Alchemy provider for CraftTS deployments.

Experimental — validate in a non-production account first. The provider now targets Alchemy 2 (2.0.0-beta.76) and delegates the final deployment to Alchemy's current CLI. The live Cloudflare/AWS hop is still not covered by this repository's tests, so run deploy preview first.

It consumes the manifest produced by @craft-ts/deploy and turns it into Cloudflare or AWS resources. It never rebuilds routes, contracts or layers, and it is never a dependency of a CraftTS application bundle.

npm install --save-dev @craft-ts/deploy-alchemy alchemy
npx craft-ts deploy preview --provider alchemy --stage staging
npx craft-ts deploy --provider alchemy --stage staging --yes

preview opens Alchemy in its read phase: it lists what would be created, updated or deleted and provably mutates nothing. deploy runs the same checks and the same preview, then refuses to apply until --yes approves the plan.

| Manifest | Resources | | ------------------------ | ---------------------------------------------------- | | static on cloudflare | Website.StaticSite | | worker on cloudflare | KV.Namespace/R2.Bucket/… then Worker | | static on aws | Website.StaticSite | | lambda on aws | Lambda.Function with its built-in Function URL | | node on aws | refused; use the Docker provider or an image preset |

Credentials are read from the environment and never written anywhere: CLOUDFLARE_API_TOKEN/CLOUDFLARE_ACCOUNT_ID (or ALCHEMY_PROFILE), or AWS_ACCESS_KEY_ID/AWS_REGION (or AWS_PROFILE). Alchemy 2 manages its state through the configured provider state store; the legacy ALCHEMY_PASSWORD is not required by this adapter.

See the Alchemy provider guide for the state, the stages, the outputs and the rollback procedure.