Fixes #1342 - #1343
Conversation
|
@ktiedt For some reason it doesn't run on Heroku, there's a log linked right into that "deployed" word above; I'm not sure if it's because it's running on a deprecated Heroku stack, since it did the job for the other stuff... https://dashboard.heroku.com/apps/ancientbeast-pr-1343/activity/builds/e9bcd5a3-64b0-4839-afa2-06e89e94fc1a |
|
weird, it installs and builds fine... but crashes in some other way... this should be fun... :( |
|
@ktiedt I recall last time this happened, was an issue with Heroku itself and they eventually fixed it. |
|
Yeah I am trying to bump it to the new stack now to test that idea. |
|
This works, removed test change for app.json and it should be safe to upgrade the stack from the dashboard to heroku-16 |
|
Noticed, had to delete the deploy for this and create a new one. Will merge in the PR and deploy master branch again to ancientbeast-beta, I guess that should trigger the upgrade to the new stack. Good job! |
This cleans up our webpack stuff a bit and streamlines it as well as properly making Phaser importable (which was needed for the properly inheriting from it later)