Upgrading from 1.x to 2.x

Pudding classes' internals work a little differently in Pudding v2.x, so an upgrade is necessary. You'll especially want to upgrade any .sol.js files that you rely on for production applications already deployed to Frontier. No data is removed in the upgrade; only the structure of the data is changed.

To upgrade your contracts, run the following. This will update your contracts in place. It's best that you commit your contracts to your code repository before upgrading just to ensure nothing is lost in case of errors.

var PuddingGenerator = require("ether-pudding/generator");
PuddingGenerator.upgrade("/path/to/source/directory", function(err) {
  // err should be null.
});

"/path/to/source/directory" is the directory containing your .sol.js files.