In addition to the Trigger Toolkit you can also use the forge command line interface to mange native module development.
Commands follow the format of:
forge module <command>
<command> is one of:
create init inspector <target> check upload versions publish <version> unpublish <version> set_current <version>
To create a new module and populate its initial files:
forge module create
To populate the initial files for a module has already been created:
forge module init
forge module inspector <target>
Valid versions for
To check your module for errors before uploading a new version:
forge module check
To upload a new version of your module:
forge module upload
To list all versions of the module that have been uploaded:
forge module versions
To publish a particular module version:
forge module publish <version>
<version> is the version number of the module you want to publish. e.g.
Note that publishing a module will make it available for use by all Trigger.IO users. This means you should only use this command if you have provided full documentation and tests for it.
To unpublish a particular module version:
forge module unpublish <version>
<version> is the version number of the module you want to unpublish. e.g.
Note that unpublishing a module version will mean any users currently using it will no longer be able to build their app. Please only unpublish versions if there is a good reason such as a major security issue.
To set a particular version of a published module as the current latest version:
forge set_current <version>
<version> is the version number of the module you want to make current. e.g.
Note that you can only use this command with published modules.