Here’s an overview of my tech and toolkit “stack” for making games with Cocos Creator.
I use JetBrains IDE Support to debug Typescript by connecting Chrome to IDEA. For this reason, I use Chrome as the default browser when testing in Cocos Creator. Fun fact though, I have only debugged a handful of times over the 11 games made with Cocos Creator.
I use inversify as dependency injection/inversion of control framework, with inversify-inject-decorators and reflect-metadata to integrate 3rd party classes into the DI through lazy injection, useful when injecting into cc.Component derived classes.
I also use @robotlegsjs/signals, a lightweight signals implementation. Dependency injection and signals provide a powerful base for the game architecture.
I use gulp for automating tasks like deployment to live/local server.
I use the Chrome/Firefox dev tools for profiling. I also use Spector.js, a Chrome extension to profile WebGL draw calls, it’s been quite useful to gain insights and optimize rendering.
I use Git for source control (with TortoiseGit integration into the Windows shell) and Redmine for issue tracking and internal wiki system.
And that’s about it.