These documents are out of date

Please visit the page on the new documentation site for up to date information.

Custom Build Processes

Throughout Truffle's history, it's clear that the default builder is not for everybody. It has some obvious caveats and is less mature than other build systems. With that in mind, Truffle provides you three ways to override the build system in order to get the most out of Truffle while also using your build process of choice.

Running an External Command

If you'd like Truffle to run an external command whenever it triggers a build, simply include that option as a string within your project configuration, like so:

module.exports = {
  // This will run the `webpack` command on each build.
  // The following environment variables will be set when running the command:
  // WORKING_DIRECTORY: root location of the project
  // BUILD_DESTINATION_DIRECTORY: expected destination of built assets (important for `truffle serve`)
  // BUILD_CONTRACTS_DIRECTORY: root location of your build contract files (.sol.js)
  // WEB3_PROVIDER_LOCATION: rpc configuration as a string, as a URL needed for web3's http provider.
  build: "webpack"

Note that you're given ample environment variables with which to integrate with Truffle, detailed above.

Providing a Custom Function

You can also provide a custom build function like the one below. Note you're given a plethora of information about your project which you can use to integrate tightly with Truffle.

module.exports = {
  build: function(options, callback) {
     // Do something when a build is required. `options` contains these values:
     // working_directory: root location of the project
     // contracts: metadata about your contract files, code, etc.
     // contracts_directory: root directory of .sol files
     // rpc: rpc configuration defined in the configuration
     // destination_directory: directory where truffle expects the built assets (important for `truffle serve`)

Creating a Custom Module

You could also create a module or object that implements the builder interface (i.e., is an object which contains a build function like the one above). This is great for those who want to maintain tighter integration with Truffle and publish a package to make everyone else's lives easier.

Here's an example using Truffle's default builder:

var DefaultBuilder = require("truffle-default-builder");
module.exports = {
  build: new DefaultBuilder(...) // specify the default builder configuration here.

Bootstrapping Your Frontend

Because you're using a custom build process, Truffle no longer knows how to bootstrap your frontend. You'll need to do this yourself. Here's a list of things your build process and/or application will need to do:

  • Include the Web3 library.
  • Initialize a web3 instance and set a provider that points to your desired ethereum client. It's important to detect if the web3 object already exists, as it might already be available if someone is viewing your application via a wallet-browser like Metamask or Mist. If the web3 object already exists, you should use that instead of initializing your own. See this example for more details.
  • require or import the built sol.js files from the ./build/contracts directory. For each .sol.js file, set the provider using the MyContract.setProvider() method. This should the same provider your web3 instance is using. Using web3.currentProvider is recommended:
var MyContract = require("./build/contracts/MyContract.sol.js");

Using Webpack

We're still working on having tighter integration with Webpack. However, checkout this example and let us know how it works for you.