To start using the Bundler, generally, you need to
The bundlet will install the Bundler into the Alfred data directory and just start working like magic. Specific implementations vary by language, so see the quickstart page for the language you're using.
If you want to implement the bundler with another language, then just use the Bash bundlet as an executable. Read below for more information.
Most assets are defined through a JSON file. The bundler includes several defaults to use, but you can add your own if necessary.
For minor updates, the Bundler will update itself automatically. These updates will include security and bug fixes, yet they might also introduce new features; however, no minor update will ever change the Bundler's API, so you needn't worry about updating your workflow to account for changes in a new minor versions.
The bundlet should never need updating; however, if a major bugfix is needed, then a post will be made, and you will need to update the bundlet in your workflow. The bundlet will work with the bundler for all minor updates of a major version (Aries, Taurus, Gemini, etc...)
We suggest reading the implementation page for more information about how to initialize the Bundler.
./alfred.bundler.sh 'utility' 'Pashua' 'latest'
./alfred.bundler.sh 'icon' 'elusive' 'fire' 'abcdef' 'true'
See the Bash documentation for more information about the arguments for loading assets and icons.
When using the Bash bundlet as an executable, pass four arguments at most to load an asset: type
name
version
json_path
. Read more about default assets.
For icons, pass five at most. Whenever you load an icon, the first argument needs to be icon
. So, if you were to pass all five, they would be
icon
font
name
color
alter
. Read more about icon arguments.
Post on the Alfred Forum thread.
Open an issue in the Github queue.