Asset Generation issues... about phaser-ce-npm-webpack-typescript-starter-project HOT 6 CLOSED

make sure to add two files with the same name but one .fnt ext and another with .png ext in assets/fonts
to create bitmapFonts
and then run $npm run assets then go and check the assets.ts File, and see if namespace BitmapFonts with yourFontName class is created or not if this is not your current problem take a screenshot of errors and post them

from phaser-ce-npm-webpack-typescript-starter-project.

#39 has been merged in with some asset generation fixes; please try the latest version out. Thanks!

from phaser-ce-npm-webpack-typescript-starter-project.

That did not fix the issue.

The issue stems from: 1337programming/webpack-shell-plugin#37

You can fix it by replacing

new WebpackShellPlugin({
  onBuildStart: ['npm run assets']
}),

with

new WebpackSynchronizableShellPlugin({
  onBuildStart: {
    scripts: ['npm run assets'],
    blocking: true,
    parallel: false
  }
}),

in your webpack config (npm install webpack-synchronizable-shell-plugin --save-dev of course)

Basically in certain conditions, the typescript compiler could start before the npm run assets was done. I'll make a merge request.

from phaser-ce-npm-webpack-typescript-starter-project.

@Nepoxx Huh, interesting, I've never encountered that one. Thanks so much for doing the research and providing the PR! Much appreciated 👍

from phaser-ce-npm-webpack-typescript-starter-project.

@rroylance I've never encountered the issue myself someone was not able to build our project due to this. Since it's a race condition it needs specific timings to occur, I think. In any case using WebpackSynchronizableShellPlugin should fix the issue :)

from phaser-ce-npm-webpack-typescript-starter-project.

Merged in. Thanks again @Nepoxx !

from phaser-ce-npm-webpack-typescript-starter-project.