Truffle v0.2.1!
Truffle v0.2.1 ships with the updated version of Pudding as well as some awesome fixes:
-
The build process's flexibility has been significantly improved. Instead of generating a
contracts.json
file,truffle deploy
will now generate Pudding classes and place them within your environment's directory. These classes are automatically bootstrapped for you when using Truffle's build process, but they can easily be included in a custom build process as well. Make sure you check out the Pudding documentation for more details. -
Contracts are now redeployed automatically with
truffle watch
andtruffle serve
. If you edit a contract, it'll automatically deploy them without you having to switch to a different terminal window. -
Truffle uses the Javascript version of solc. You no longer have to install
solc
yourself or deal with the hassle of getting it working with your RPC client. Instead, Truffle will use the Javascript version ofsolc
, making your life a whole lot easier. -
Web3 has been bumped up to 0.14.0. Hooray!
-
You can now use the
import_headers
statement in solidity files:import_headers "MyOtherContract";
Instead of importing the whole file, this will just include an abstract version, reducing your contract's gas costs if your contract doesn't need to create new instances of
MyOtherContract
. -
You can now run a single test file instead of running all of them. It's easy:
$ truffle test ./path/to/test/file.js
-
Post-processor changes:
inject-contracts
processor has now been renamed tobootstrap
, which better describes what it does (it bootstraps browser-based dapp frontends).include-contracts
processor has been added which is useful for including your contracts in node-based libraries.
-
Advanced web3 and provider configuration has been removed. We've removed the advanced web3 and provider information because they seriously cluttered the codebase. If you want a frontend with advanced configuration, you'll instead need to use your own build process.
Embarking on a New Journey
With the most recent release of Embark v1.0.2, Truffle and Embark do things in very similar ways, and so it no longer makes sense to keep maintaining two separate codebases. To that end, Truffle and Embark will join forces and ideally merge our efforts sometime in the future. We're not sure what the landscape of this merge will look like yet, but we're sure that it'll bring the great features of both frameworks together and offer greater support for everyone.