Your apps can be deployed to Slack's managed infrastructure by executing slack deploy at the root of your project.
When you execute slack deploy, the CLI will package up your app and deploy it to the workspace you specify. At that point, anyone in your workspace will be able to find and add your app by navigating to Apps > Manage > Browse apps.
No local development server is started with slack deploy.
When deploying your app to a Slack Enterprise Grid, you may specify a workspace within your organization to grant your app access to with the --org-workspace-grant flag.
npm dependencies cannot be used in code deployed to Slack, as npm dependencies are not yet supported in deno bundle. Stay tuned for npm support in a future Deno release.
To distribute a function so that another user (or group of users) can build workflows that reference your function after you deploy your app, you can execute the slack function distribute command. After choosing your workspace, you'll also be prompted to select which function you want to deploy, as well as who you would like to give access to your function -- app collaborators only, specific users, or everyone. Your function will then be distributed to those users the next time you deploy your app.
β¨ For more information about distributing functions, refer to distribute a custom function.
If you need to make any changes to your app, you must redeploy it using slack deploy.
In addition, if administrators of your workspace have enabled admin-approved apps, it means your app will need approval before it can be deployed or redeployed to your workspace.
β¨ For more information about getting your app approved, check out access controls for developers.
Have 2 minutes to provide some feedback?
We'd love to hear about your experience building modular Slack apps. Please complete our short survey so we can use your feedback to improve.