melonjs-deployment

1# Starting and shipping a project
2 
3## Scaffolding
4 
5Start from the template rather than assembling a build by hand:
6 
7```bash
8npm create melonjs@latest my-game
9```
10 
11The project name is required — without it the command prints its usage and
12exits. It downloads the melonJS TypeScript boilerplate (Vite, TypeScript and the
13debug plugin already wired in), which saves you the top-level-await and
14asset-path issues that a hand-rolled config usually hits first.
15 
16## Adding melonJS to an existing project
17 
18```bash
19npm install melonjs
20```
21 
22```js
23import { Application, Sprite, loader } from "melonjs";
24```
25 
26The package is a tree-shakeable ES module with TypeScript declarations included
27and **no runtime dependencies**.
28 
29A CDN build exists for quick experiments, but not for production:
30 
31```html
32<script type="module">
33    import { Application } from "https://cdn.jsdelivr.net/npm/melonjs@20/+esm";
34</script>
35```
36 
37## Browser support and transpiling
38 
39The published bundle targets **ES2022** and uses private class members. A browser
40that predates that **cannot parse the file at all** — it fails at load, not when
41a feature is used, so the symptom is a blank page with a syntax error.
42 
43To support older browsers, transpile melonJS **together with your own code**.
44The usual trap is that build setups skip `node_modules` by default, leaving
45melonJS untouched however low you set your target:
46 
47```js
48// vite.config.js — esbuild downlevels dependencies too
49export default { build: { target: "es2020" } };
50```
51…