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

@thegreataxios/pulumi-railway

v0.1.2

Published

Native Pulumi provider for Railway: projects, services, environments, variables, custom domains, volumes, and buckets

Readme

@thegreataxios/pulumi-railway

npm CI License: MIT

An experimental native Pulumi provider for a subset of Railway: projects, services, environments, environment variables, custom domains, volumes, and object-storage buckets. It provides CRUD, drift detection, import, and replacement semantics on immutable fields.

Status

This provider is pre-1.0 and is not listed in the Pulumi Registry. The TypeScript/Node.js SDK is the only SDK published as a package. Deployment triggers, Railway-provided domains, TCP proxies, and lookup functions are not implemented yet.

Go, Python, and .NET users can generate local SDKs from the installed plugin:

pulumi package gen-sdk railway --language go
pulumi package gen-sdk railway --language python
pulumi package gen-sdk railway --language dotnet

Supported resources

| Resource | Description | | --- | --- | | railway.Project | Railway project and default environment | | railway.Environment | Named project environment (staging, previews) | | railway.Service | Service source and per-environment runtime configuration | | railway.Variable | Service or shared environment variable | | railway.CustomDomain | Custom domain, DNS verification, and certificate status | | railway.Volume | Persistent volume and mount path | | railway.Bucket | S3-compatible object storage bucket |

Installation

Requires the Pulumi CLI and Node.js 20 or newer.

npm install @thegreataxios/pulumi-railway

The SDK downloads the matching pulumi-resource-railway binary from this repository's GitHub releases.

Authentication

Use one authentication method:

# Account or workspace token
pulumi config set --secret railway:token <token>

# Or a project token
pulumi config set --secret railway:projectToken <token>

The provider also reads RAILWAY_API_TOKEN for account/workspace tokens and RAILWAY_TOKEN for project tokens. If both token types are configured, the provider returns an error rather than choosing one implicitly.

Create account/workspace tokens at https://railway.com/account/tokens.

Usage

import * as railway from "@thegreataxios/pulumi-railway";

const project = new railway.Project("my-project", {
  name: "my-app",
  // Strongly recommended: projects created without a workspace ID are
  // temporary public projects that expire after 24 hours unless claimed.
  // Find yours in the Railway dashboard under workspace settings.
  workspaceId: "your-workspace-id",
});

const web = new railway.Service("web", {
  projectId: project.id,
  environmentId: project.defaultEnvironmentId,
  name: "web",
  image: "node:20-alpine",
  startCommand: "node server.js",
  healthcheckPath: "/health",
  numReplicas: 2,
});

new railway.Variable("database-url", {
  projectId: project.id,
  environmentId: project.defaultEnvironmentId,
  serviceId: web.id,
  key: "DATABASE_URL",
  value: "postgresql://...",
});

new railway.CustomDomain("api", {
  projectId: project.id,
  environmentId: project.defaultEnvironmentId,
  serviceId: web.id,
  domain: "api.example.com",
  targetPort: 8080,
});

new railway.Volume("data", {
  projectId: project.id,
  environmentId: project.defaultEnvironmentId,
  serviceId: web.id,
  mountPath: "/data",
  name: "app-data",
});

export const projectId = project.id;
export const serviceId = web.id;

Changing a service's repository, branch, project, or environment replaces the service. Image changes update the existing service in place. Parent identifiers and other immutable identity fields on all resources also use replacement semantics.

Variable creation is create-only. If the same key already exists in Railway, creation fails instead of overwriting it. Import the existing variable first, then let Pulumi update it.

Import

pulumi import railway:index:Project project <project-id>
pulumi import railway:index:Environment staging <project-id>/<environment-id>
pulumi import railway:index:Service web <service-id>/<environment-id>
pulumi import railway:index:Variable nodeEnv <project-id>/<environment-id>/<service-id>/<key>
pulumi import railway:index:Variable shared <project-id>/<environment-id>//<key>
pulumi import railway:index:CustomDomain api <domain-id>/<project-id>/<environment-id>/<service-id>
pulumi import railway:index:Volume data <volume-id>/<project-id>
# If a volume has more than one attachment, qualify the import:
pulumi import railway:index:Volume data <volume-id>/<project-id>/<environment-id>/<service-id>
pulumi import railway:index:Bucket uploads <project-id>/<environment-id>/<bucket-id>

Development

Requirements:

  • Go version declared in provider/go.mod
  • Node.js 20 or newer
  • Pulumi CLI
  • GNU Make, jq, and golangci-lint v2
make build          # Build the provider binary
make schema         # Generate schema.json
make sdk            # Generate the TypeScript SDK
make nodejs-lock    # Refresh the committed SDK lockfile after metadata changes
make package-nodejs # Build and pack the npm artifact into dist/
make ci             # Tests, lint, codegen drift, SDK package, and example typecheck
make release-snapshot VERSION=0.1.0 # Verify all release archives locally

Generated schema and SDK metadata come directly from the provider. They use the root railway:index:* module, npm package @thegreataxios/pulumi-railway, and the GitHub release plugin source. No machine-local paths or platform-specific post-processing are used.

Releases

Push a semantic version tag such as v0.1.0. The release workflow:

  1. Runs the complete validation suite.
  2. Builds provider archives for Linux, macOS, and Windows on amd64 and arm64.
  3. Publishes the archives and checksums to a GitHub release.
  4. Publishes the matching public npm package with provenance.

Configure the NPM_TOKEN GitHub Actions secret before creating the first tag. The npm version and GitHub tag must match.

Prereleases such as v0.1.0-alpha.1 are published to npm with the next dist-tag. Stable semantic versions use the default latest dist-tag.

See CHANGELOG.md for user-visible changes.

Railway API

License

MIT