"Game development Log" Upgrade of node. JS Dependency Package-raised bug

One of our games is ready to go online, and for the last few weeks we've been preparing for the launch. Due to the long development cycle of this game, the server is using node. JS Development, several of which are older and ready to upgrade before going online.

The upgrade includes the CRC and Async 2 packets, did not expect the 2 common package API has been changed, resulting in a bug in the game server, spent half a day to troubleshoot the problem.

First CRC, we use CRC.CRC32 to calculate the difference in the comparison configuration file, the value returned in the previous old version is a signed 32-bit integer, and the new version has become unsigned 32-bit integer.

The Async.auto function can automatically arrange the execution order of asynchronous methods based on dependency, but the original callback function signature is first CB after results, the new version has been changed to first results after CB.

Upgrading a dependent package is risky and must be tested in place after the upgrade.

"Game development Log" Upgrade of node. JS Dependency Package-raised bug