How to write extensions

There are three stages to developing an extension:

1. Set up the basic scaffolding.
2. Develop your extension and debug it.
3. Package and publish your extension for others to use.

Read the sections linked above for details!

Creating an Extension

• Open your extensions folder by selecting "Help > Show Extensions Folder" in Brackets
• Inside the user folder, create a new "yourExtensionName" folder, and inside that create a main.js file.
• For a quick start, you can paste in the Simple "Hello World" extension or the code from an existing extension that is similar to what you want to do.
• If you're working on anything big we recommend you post to the brackets-dev Google group or the #brackets IRC channel on freenode early on so you can get feedback (there may be others working on similar ideas!).

Testing/Debugging Workflow

• Edit your main.js file.
• Save the file and restart Brackets via "Debug > Reload Brackets" to see your changes.
• To debug problems, use "Debug > Show Developer Tools" (opens as a tab in Chrome). You can use console.log(), set breakpoints, etc.
  • The first time you open Developer Tools, you must disable caching - otherwise using Reload while dev tools are open will not reflect changes to your extension.

See Debugging Brackets for a more robust two-window workflow.

You can also [write unit tests for your extension](Extension Unit Tests).

Publishing Extensions

1. Add a package.json file next to your main.js
2. ZIP up your entire extension folder (the GitHub "Download ZIP" button is handy for this)
3. Publish your extension by uploading the ZIP to the Brackets Extension Registry

For more, see Extension Registry Help.

Common How-Tos

Using modules

• To load modules from your extension's folder tree, use require() with a path relative to your extension's root folder.
• To load modules from Brackets core, use brackets.getModule() with a path relative to the Brackets src root.
• You cannot load modules from other extensions (yet).

You can also use other files packaged inside your extension - for example, see "Load a CSS file" below.

Adding menu items & keyboard shortcuts

See Simple "Hello World" extension for a code sample.

For any new behavior, first register a Command that implements your behavior, via CommandManager.register(). This just maps a Command id (string) to your handler function. Use package-style naming for your Command id (e.g. "myorg.myextension.mycommand") to avoid collisions with other extensions. (See also: [higher-level overview of command architecture](Brackets Development How Tos#wiki-commands)).

Add a menu item: Get a top-level menu by calling Menus.getMenu() with one of the AppMenuBar constants (currently FILE_MENU, EDIT_MENU, VIEW_MENU, NAVIGATE_MENU or HELP_MENU). Then add a menu item via theMenu.addMenuItem(), linking it to your Command id. The menu item's label will be the string name you gave the Command when it was created.

As a convenience, addMenuItem() also lets you create a keyboard shortcut for your Command at the same time.

Add a context menu item: Get a context menu by calling Menus.getContextMenu() with one of the ContextMenuIds constants (currently EDITOR_MENU, INLINE_EDITOR_MENU, PROJECT_MENU or WORKING_SET_MENU). Then add a menu item via theContextMenu.addMenuItem(), linking it to your Command id exactly like a top level menu item.

Add a menu divider Get a top level or context menu as explained above. Then add a menu dividers via theMenu.addMenuDivider(). It will default to the last position currently in the menu. You have the option of placing it with the position parameter first and last, which will place the divider accordingly. Additionally, you can set position parameter to before and after, pass in a Command ID, and place the divider accordingly.

Add a keyboard shortcut: To add a keyboard shortcut without any related menu item, call KeyBindingManager.addBinding() directly, linking a shortcut to your Command id. Be sure to use the Brackets Shortcuts page to see which shortcuts are available and to add the shortcuts that you use to the list.

To decline a keyboard event and allow other parts of Brackets to handle it, make your Command handler return a $.Promise that is already rejected at the time you return it. (This is useful if you want to override editing keys like Enter only when the cursor lies in certain places, and allow the default behavior in other cases; or always override a key in the code editor but allow default behavior in simpler textfields). (Note: requires Sprint 18 or later)

Adding new UI elements

This is unofficial API - adding UI elements directly through the DOM works, but puts you on shaky ground. Code that does this will break as Brackets updates evolve the UI. The only official way to extend the Brackets UI is through JavaScript APIs, such as the Menu interface above or the Quick Edit interface below.

However, following these best practices will ensure your code behaves as nicely as it possibly can under the circumstances:

Add a panel below the editor: Use the CSS class .bottom-panel; see the JSLint bottom-panel.html for an example. Add your panel above the status bar using PanelManager.createBottomPanel("yourExtension.name", $(panelHtml)). You may see Resizer.makeResizable() and manual DOM insertion of panels in some extensions but this practice is being phased out since the introduction of PanelManager.

Add a toolbar icon: Use $myIcon.appendTo($("#main-toolbar .buttons")).

Add a top panel/toolbar: Use $myPanel.insertBefore("#editor-holder").

UI design: Be sure to follow the Extension UI Guidelines.

Load a CSS file: use ExtensionUtils.loadStyleSheet(). It returns a Promise you can use to track when the CSS is done loading.
To avoid accidentally breaking core Brackets UI, place a CSS class on the root of your UI and make sure all your CSS rules include a descendant selector. E.g. instead of li { ... } use .myExtension li { ... }.

Extending specific Brackets features

Quick Edit (inline editors): To create an extension that responds on Ctrl+E (like the inline color picker), use EditorManager.registerInlineEditProvider(). If multiple "providers" all want to respond in a given context, however, the first one wins - there's no notion of priority or cycling through providers yet.

Quick Docs: Similar to Quick Edit, but register your provider with EditorManager.registerInlineDocsProvider() instead.

Quick Find Definition: To provide quick symbol navigation for a new language, use QuickOpen.addQuickOpenPlugin(). Register for a specific language id and only return true from match() when an "@" prefix is present (see CSS support for a simple example).

Quick Open: To add a new global search feature (like Quick Open), use QuickOpen.addQuickOpenPlugin() with an empty languageIds array. Pick a new, unique prefix for match() to respond to, and register a new command that invokes QuickOpen.beginSearch() with your custom prefix. (See the File Navigation Shortcuts extension for a simple example).

Code Hints: To create an extension that shows a code hint popup, use CodeHintManager.registerHintProvider(). Unlike Quick Edit, these "providers" can have varying priority to resolve conflicts; more specific providers take precedence.

Syntax Coloring: Extensions can add new code-coloring "modes" via LanguageManager.defineLanguage(). See Language Support for details.

Accessing resources (e.g. images) in your extension

Extensions can get installed at (semi-)arbitrary paths. For example, you might develop your extension in the brackets/src/extensions/dev/foo directory, but a user might install it in /Users/<user>/Library/Application Settings/Brackets/extensions/user/bar.

Thankfully, the require context that's passed in to your extension's main.js file can help you resolve paths. Just call require.toUrl with the relative (to your module) path you'd like to make relative to the site root. IMPORTANT: Make sure you're using the require object that was passed to your module, not the global require object.

For example, if you have awesome.jpg in your extension's top-level foo folder, you can do require.toUrl('./awesome.jpg'), and it will return something like /extensions/dev/foo/awesome.jpg when you call it and /Users/<user>/Library/Application Settings/Brackets/extensions/user/bar/awesome.jpg when your user calls it. The path you give toUrl should be relative to your extension's top-level folder (yes, subdirectories work), and the URL you get back will be relative to the site root (i.e. it will begin with "/").

Accessing Node APIs

Brackets includes a built-in Node.js server that runs as a side process. Your extension can include code that runs in Node – accessing useful Node APIs and pulling in helpful NPM libraries. Read more on running code in Brackets' Node instance...

Further reading

For more on Brackets APIs and architecture, see Brackets Development How Tos.

If you're interested in contributing to the core Brackets codebase, see How to Hack on Brackets.