This repo contains all the official Botpress modules.
🚧 These are only meant to be compatible with Botpress X
Starting from Botpress X, modules are published on npm under the @botpress/ organization.
| Module | Status | Installation |
|---|---|---|
| @botpress/nlu | Ready | npm install --save @botpress/nlu |
| @botpress/analytics | Ready | npm install --save @botpress/analytics@beta |
| @botpress/broadcast | Ready | npm install --save @botpress/broadcast@beta |
| @botpress/channel-messenger | NOT READY | npm install --save @botpress/channel-messenger@beta |
| @botpress/channel-microsoft | Ready | npm install --save @botpress/channel-microsoft |
| @botpress/channel-slack | NOT READY | npm install --save @botpress/channel-slack |
| @botpress/channel-telegram | NOT READY | npm install --save @botpress/channel-slack |
| @botpress/channel-twilio | Ready | npm install --save @botpress/channel-twilio@beta |
| @botpress/channel-web | Ready | npm install --save @botpress/channel-web@beta |
| @botpress/channel-hitl | NOT READY | npm install --save @botpress/channel-web@beta |
| @botpress/channel-scheduler | Ready | npm install --save @botpress/channel-ready@beta |
| @botpress/skill-choice | Ready | npm install --save @botpress/channel-ready@beta |
| @botpress/terminal | Ready | npm install --save @botpress/channel-terminal@beta |
If you are willing to test package before publishing it you can do it in a following way (this is a workaround that could be fixed in the future within yarn itself):
- Clone
botpresspackage navigate to it and runyarn linkwithin that folder - Navigate to appropriate directory like
packagesand runyarn - Run
yarn link botpressto make your development instance ofbotpressavailable within packages - You can now link packages to the bot by running
yarn linkwithin package directory and thenyarn link <package-name>within your bot directory