Ensure you have Node.js installed, then install all the build dependencies in the folder where you cloned the repository :
$ [sudo] npm install
npm run dev
to start the dev server on watch mode atlocalhost:9000
.npm run build
to generate a minified, production-ready build, in thepublic
folder
if everything goes well, on running the dev server for the first time you should see this :
Note: when generating the production build, Webpack will attempt to filter files under the data folder to only copy final assets and ignore project files (e.g. .ftpp project files from Free Texture Packer). If you find your file being wrongly ignore you can easily add the corresponding extension in the webpack.config.js file
src
└── data
│ ├── bgm
│ ├── fnt
| ├── img
| ├── map
| └── sfx
└── js
| ├── renderables
| └── stage
├── index.js
├── index.css
├── index.html
├── manifest.js
public
├── data
├── bundle.js
└── index.html
src
- the root folder for your game source code
- The entry file is index.js.
- index.css and index.html are default templates that can be customized
- manifest.js is a list of asset to be preloaded by melonJS (these won't be automatically imported and bundled by webpack)
src/js
- add your source classes here
src/data
- where to add your game assets
public
- where the production-ready build files will be copied/generated when using
npm run build
- where the production-ready build files will be copied/generated when using
In development mode, the boilerplate will automatically register and instantiate the melonJS Debug Plugin
If you need technical support, you can contact us through the following channels :
For any other non technical related questions, feel free to also send us an email.