You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -507,6 +507,22 @@ If you want to deploy to the livenet then after configuring you account on ```co
507
507
508
508
To deploy a dapp to SWARM, all you need to do is run a local SWARM node and then run ```embark upload swarm```.
509
509
510
+
Plugins
511
+
======
512
+
513
+
It's possible to extend Embarks functionality with plugins. For example the follow is possible:
514
+
515
+
* plugin to add support for es6, jsx, coffescript, etc (``embark.registerPipeline``)
516
+
* plugin to add standard contracts or a contract framework (``embark.registerContractConfiguration`` and ``embark.addContractFile``)
517
+
* plugin to make some contracts available in all environments for use by other contracts or the dapp itself e.g a Token, a DAO, ENS, etc.. (``embark.registerContractConfiguration`` and ``embark.addContractFile``)
518
+
* plugin to add a libraries such as react or boostrap (``embark.addFileToPipeline``)
519
+
* plugin to specify a particular web3 initialization for special provider uses (``embark.registerClientWeb3Provider``)
520
+
* plugin to create a different contract wrapper (``embark.registerContractsGeneration``)
521
+
* plugin to add new console commands (``embark.registerConsoleCommand``)
522
+
* plugin to add support for another contract language such as viper, LLL, etc (``embark.registerCompiler``)
523
+
524
+
For more information please see the [plugin documentation](http://embark.readthedocs.io/en/latest/plugins.html)
0 commit comments