Embark is now part of Status and we are happy to announce Embark 3.0 by Status!
Embark has a new website and up to date documentation which can be found at https://embark.status.im/docs/
Besides Solidity, Embark now also supports Vyper out of the box, as well as Bamboo through an embark plugin
You can use these languages side by side, and take advantage of Embark’s features such as contract testing just like you would with Solidity.
From the dapp side, contracts and libs like EmbarkJS can be implicitly imported, for e.g to import a contract:
import SimpleStorage from 'Embark/contracts/SimpleStorage'
import EmbarkJS from 'Embark/EmbarkJS'
Or a initialized web3 instances (with the config of
import web3 from 'Embark/web3'
The typical ES6 imports will also simply work. You can even import directly css files inside js files:
import React from 'react';
Although Embark is focused on DApps, it can perfectly be used for projects targeting only smart contracts and no other components.
There is a now a template to create a simple project with all the components disabled except smart contracts:
embark new AppName --simple
You can also fine tune this in embark.json by specifying the config of each component or setting it to false if you don’t want it.
embark graph will generate a ER graph of the dapp contracts. This takes into account not just the inheritance but also the relationships specified in the configuration.
Embark now supports referencing directly URIs including http, git, github, or directly files contained in other directories than the ones specified in embark.json
Embark is smart enough to take care of the dependencies of the resources and present them in a consistent manner to the compiler, it just works!
You can also import the same URIs directly in solidity which is quite useful for interfaces, e.g:
You can now install npm packages that contain contracts (e.g
npm install --save openzeppelin-solidity) and refer them to them in the contracts.json file:
or even import them directly in solidity without the need for the config:
The demo app has been updated to reflect the new structure. It also now uses ReactJS which provides a good example on how to use React with Embark.
Embark now uses web3.js 1.0 in all layers, including in the console and in contracts testing.
A new config called
afterDeploy is available and it can be used to specify actions to run after all contracts have been deployed.
It’s possible to also specify the specific account to deploy from using the directive
The versions config has been moved to embark.json, the download mechanism has also been fastly improved under the hood:
In the tests you can now specify a mnemonic:
It’s also possible to specify a node, in case you don’t want to run in the internal vm:
Swarm is now completely integrated on-par with IPFS. You can use interact with Swarm on the dapp side, as well as upload your dapp to Swarm.Swarm
For a complete list please refer to the release notes in github
To discuss about Embark or Dapp development, please join us at the gitter channel