Deploying to Production

Overview

Transitioning from development to production is a critical step for any application. JopiJS is designed to make this transition as seamless as possible by eliminating the need for complex build pipelines.

In this guide, you will learn:

• How to switch to Production Mode.
• Why JopiJS doesn't require a Build Step.
• How production mode impacts your dependencies and performance.

1. Enabling Production Mode

JopiJS follows the industry-standard convention for Node.js and Bun.js applications. To switch to production, you must set the NODE_ENV environment variable.

Using the environment variable

When starting your server, simply prefix your command:

NODE_ENV=production bun run start

Checking the status

When your server starts, JopiJS displays a message in the console if you are in development.

2. The "No Build" Philosophy

Unlike frameworks like Next.js, JopiJS has no separate "build" command.

In traditional frameworks, you must run a build step to transpile, minify, and optimize your code before deployment. JopiJS eliminates this step entirely.

How is this possible?

1. Ultra-Fast Internal Bundler: JopiJS uses an extremely optimized internal bundler that generates production-ready code on the fly with incredible speed.
2. Smart JIT Compilation: Assets and components are optimized exactly when they are needed.
3. Intelligent Server-Side Caching: JopiJS manages a sophisticated cache to optimize the conversion from React components to HTML.

3. Performance Benchmarks

This architectural choice isn't just about convenience—it's about raw performance.

Summary of Deployment Steps

1. Configure your Public URL.
2. Set NODE_ENV=production.
3. Start your server with bun run start (or npm start).
4. (Optional) Set up a Reverse Proxy for SSL and load balancing.