Phaser es6/webpack + PhaserInput

Lately I’ve been trying to work a little bit more with Phaser in my free time since we use it a work a bit.

Luckily for me, Leandro Cabrera has created a boilerplate project which allows me to write and structure phaser games in a sane way.

Also luckily for me, Azerion maintains a plugin for a feature that I feel should just be part of Phaser’s core, text input.

Unluckily for me, these two code bases do not like play together out of the box.

After a bit of googling around I found several posts where people were encountering the same problems as me but none of the solutions worked.

Luckily a few posts provided a starting point and I was finally able to get them to play together.

Firstly in our webpack.config.js we need to make some edits to our module rules and alias objects

module: {
    rules: [
      { test: /\.js$/, use: ['babel-loader'], include: path.join(__dirname, 'src') },
      { test: /pixi\.js/, use: ['expose-loader?PIXI'] },
      { test: /phaser-split\.js$/, use: ['expose-loader?Phaser'] },
      { test: /p2\.js/, use: ['expose-loader?p2'] },
      { test: /phaser\-input\.js$/, use: "exports-loader?PhaserInput=PhaserInput"}
  node: {
    fs: 'empty',
    net: 'empty',
    tls: 'empty'
  resolve: {
    alias: {
      'phaser': phaser,
      'pixi': pixi,
      'p2': p2,
      "phaser-input": path.join(

Then in our Boot state (or where ever, I just like plugin initialization there), we can import the class like this :

import PhaserInput from'phaser-input'

And finally in our init we add the plugin to Phaser;

The double PhaserInput when adding the plugin in more than a little annoying but at the moment I’m just happy to have these two necessary code bases working together

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.