Change Windows "Generate Dev Bundle" script to use common globals. #8505
This change allows the Windows "Generate Dev Bundle" script to
This behavior now works in a similar way as the
Hopefully this will prevent a mistake like this in the future!
This change allows the Windows "Generate Dev Bundle" script to automatically get the versions of major bundled versions from the same script which the Unix script uses, thus preventing different versions of Node.js, npm, Mongo, etc. from being built into different versions of Meteor, such as what happened when I published Meteor 184.108.40.206 and failed to notice the duplication of variables across different scripts. This behavior now works in a similar way as the 'BUNDLE_VERSION' variable, which is retrieved from the global `meteor` script except this change uses the package versions from the `build-dev-bundle-common.sh` script in the `scripts` directory.
In a similar fashion as: * f51c682 (Node.js) * 8ea4158 (npm) * 3470516 (MongoDB) I overlooked the multiplicity of these version variables when updating the major package versions during the release of Meteor 220.127.116.11. While I intend on never making this mistake again, I've also opened #8505 which consolidates these variables to a single location (in `build-dev-bundle-common.sh`) to hopefully prevent this from happening to anyone else!