Phaser: 【typescript】npm @types support

Created on 29 Jan 2017 · 2Comments · Source: photonstorm/phaser

I think you should use @types from typings
If you use @types, it will be easier

Sorry I'm not good in English.

Source

kgtkr

👍2

Most helpful comment

@photonstorm Hey! I notice that you now officially ship typings for Phaser3.
Do you have any plans on adding those to @types?
I'd like to use them with VSCode but I can't find anything about this issue and this seems like the only option I have.

Telokis on 9 May 2018

👍7 ❤4

All 2 comments

Thank you for taking the time to open this issue. However, official support for Phaser 2 has now ended as we focus on preparing Phaser 3 for beta release. In a bid to keep the project tidy, and avoid confusion, we are closing all v2 related issues.

This does not mean your issue won't be looked-at. In November 2016 the Phaser CE (Community Edition) project began. The aim of Phaser CE was to allow the community to continue v2 development. Since then it has gained significant traction, with many updates and releases.

If you are still interested in having your issue investigated we strongly recommend testing the latest Phaser CE release. And only if the problem persists, opening an issue on the Phaser CE repo.