---
title: "Fly.io ❤️  JS"
description: "Fly.io proposes a general-purpose way to deploy JavaScript and Node.js applications despite the ecosystem’s many frameworks, package managers, runtimes, and TypeScript conventions. Its dockerfile-node project uses package.json, lockfiles, and dependency metadata to generate a baseline Dockerfile, .dockerignore, and optionally a docker-entrypoint script; users can invoke it with npx @flydotio/dockerfile. Conditional EJS templates accommodate framework-specific requirements, with initial templates for Express, Fastify, Gatsby, Nest, Next, Nuxt, and Remix, though current support may extend only to a splash screen. Future plans include replacing Fly.io’s existing flyctl scanners, integrating deployment-time secrets, volumes, databases, and health checks, and adding customization such as build caching, swap, Docker Compose generation, browser setup, and non-root execution."
---

# Fly.io ❤️  JS

[Fly.io](https://yomu.fyi/company/fly-io) · Apr 24, 2023

**Type:** Announcement

## Summary

Fly.io proposes a general-purpose way to deploy JavaScript and Node.js applications despite the ecosystem’s many frameworks, package managers, runtimes, and TypeScript conventions. Its dockerfile-node project uses package.json, lockfiles, and dependency metadata to generate a baseline Dockerfile, .dockerignore, and optionally a docker-entrypoint script; users can invoke it with npx @flydotio/dockerfile. Conditional EJS templates accommodate framework-specific requirements, with initial templates for Express, Fastify, Gatsby, Nest, Next, Nuxt, and Remix, though current support may extend only to a splash screen. Future plans include replacing Fly.io’s existing flyctl scanners, integrating deployment-time secrets, volumes, databases, and health checks, and adding customization such as build caching, swap, Docker Compose generation, browser setup, and non-root execution.

## Context

The JavaScript and Node.js ecosystem presents many frameworks, package managers, runtime alternatives, and deployment conventions. Fly.io has community-contributed templates for only a small number of Node frameworks, with uneven attention, motivating a more general deployment approach.

## Approach / What changed

The dockerfile-node project inspects package.json, dependency metadata, and lockfiles such as yarn.lock and pnpm-lock.yaml to generate a baseline Dockerfile. EJS conditionals adapt generated files to framework-specific requirements, while the command can also create or replace .dockerignore and optionally add a docker-entrypoint script.

## Takeaways

- The generated Dockerfile supports package-manager differences by checking for yarn.lock and pnpm-lock.yaml; TypeScript is treated as a devDependency and handled during the build step.
- Initial framework templates cover Express, Fastify, Gatsby, Nest, Next, Nuxt, and Remix, while tRPC, Strapi, RedwoodJS, SvelteKit, and KeystoneJS remain blocked by framework-specific issues.
- Planned customization includes build caching, swap allocation, Docker Compose generation, automatic Chrome or Chromium setup for Puppeteer, and framework-aware non-root execution.

**Tags:** [Docker](https://yomu.fyi/topic/docker), [Fly.io](https://yomu.fyi/topic/fly-io), [JavaScript](https://yomu.fyi/topic/javascript), [Node.js](https://yomu.fyi/topic/node-js)

- Source: [Fly.io](https://fly.io/blog/flydotio-heart-js)
- Source URL: https://fly.io/blog/flydotio-heart-js
- Ingested by Yomu: 2026-09-03T01:25:44.784Z

[Read original post](https://fly.io/blog/flydotio-heart-js)