skills.rest
qfeius
qfeiusOFFICIAL
Explore all skills by this author →
GitHub

make-app-runtime

Validates Make App workspace manifests, build artifacts, and Service runtime entry contracts.

5|Updated Apr 1, 2026
Search Tags:#build artifacts#publish readiness#runtime contract#pnpm workspace#make app#node versioning#service entrypoint
One-click install
npx skills add https://github.com/qfeius/make-platform-skills --skill make-app-runtime-qfeius
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-app-runtime
Source: https://github.com/qfeius/make-platform-skills/tree/main/skills/make-app-runtime
Command: npx skills add https://github.com/qfeius/make-platform-skills --skill make-app-runtime-qfeius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Make App projects fail at publish time when workspace manifests, build outputs, or Service entrypoints drift from the platform image contract, producing errors like "Cannot find module '/app/apps/service/dist/server.js'". This Skill enforces the fixed runtime baseline so generated or refactored Apps build and start correctly in Docker/K8s environments. ## Core Features & Use Cases - Workspace and package manager contract enforcement: Verifies apps/package.json, apps/pnpm-workspace.yaml, and child manifests declare Node.js 22.20.0, Corepack 0.34.0, and pnpm 10.20.0, with all commands run through Corepack. - Service runtime and build contract checks: Ensures apps/service compiles src/server.ts to dist/server.js, starts with node dist/server.js on port 3000, and includes a contract test protecting the runtime entry. - Publish-readiness gates: Defines check:publish and verify:publish scripts covering runtime version checks, builds, auth and permission audits, gateway-mode contract tests, and artifact verification before makecli app deploy. - Use Case: When a deployed Make App crashes with a missing dist/server.js error, use this Skill to diagnose whether the build never ran, tsconfig emitted elsewhere, or the start script points at a file the build does not create, then fix the build/start contract. ## Quick Start Use the make-app-runtime skill to audit my Make App workspace and fix the publish-readiness contracts before deployment.

Frequently Asked Questions about make-app-runtime

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix the 'Cannot find module /app/apps/service/dist/server.js' error?▼

This error means the Service build/start contract broke: the build never ran, src/server.ts is missing, tsconfig emitted elsewhere, or the start script points at a file the build does not create. Run the Service build with corepack pnpm --filter <service-package> build and verify apps/service/dist/server.js exists.

What Node and pnpm versions does a Make App workspace require?▼

Newly generated Make App workspaces require Node.js 22.20.0, Corepack 0.34.0, and pnpm 10.20.0. The apps/package.json must declare packageManager [email protected] and matching engines, plus a .nvmrc containing exactly 22.20.0.

How do I verify a Make App is ready to publish before makecli app deploy?▼

Run the project-local verify:publish script, which chains runtime version checks, tests, the auth contract audit, build artifact verification for apps/ui/dist and apps/service/dist/server.js, and a schema diff. Deploy success alone does not prove publish readiness.

Can I use a globally installed pnpm for Make App builds?▼

No. All project commands must run through Corepack as corepack pnpm so the version declared in packageManager is used. A globally installed pnpm, including a newer major version, must not be used for a Make App.

What port should the Make App Service run on?▼

The Service HTTP port is fixed at 3000. Generated code, .env.example, docs, health checks, tests, CORS, and UI local Service base URL examples must all align to 3000; if the port is occupied locally, report the conflict rather than changing the contract.

When should I migrate an existing Make App to the Node 22.20.0 runtime?▼

Only when the user explicitly requests a runtime migration. Existing Apps keep their declared Node and pnpm versions during unrelated UI, auth, filtering, Service, or DSL work, and any migration should be a dedicated change with tests and a Preview deployment.

Related Skills

Explore More Software Engineering Skills→
zhu637882-stackzhu637882-stack

env-setup

Detect, install, and configure Homebrew, Node.js, pnpm, PostgreSQL, Redis, Git, then output a summary.

Community
Advanced
robotijnrobotijn
3

vercel-deploy

Automate Vercel deployment configuration for Next.js 15 App Router apps.

Community
Advanced
VictorSmaniottoVictorSmaniotto

auth-rbac

Implement Laravel RBAC with Guards, Policies, Gates, and Spatie permissions.

Community
Advanced
edercnjedercnj

micronaut-scaffold

Scaffold Micronaut service modules with hexagonal architecture and Docker support.

Community
Intermediate