- Colours of Handlebars expressions are selected to be in contrast with the surrounding HTML.
- Handlebars expressions get syntax highlighting in HTML attributes.
- Parameters passed to block expressions get syntax highlighting too.
- Works both with individual template files and inline templates in script tags.
- Key bindings for
{{! Handlebars comments }}(Sublime only) - Tab triggers for
if→{{#if }}ifel→{{#if }} {{else}}el→{{else}}elif→{{else if }}un→{{#unless }}ea→{{#each }}wi→{{#with }}par→{{> }}(for partials)x-temp→<script type="text/x-handlebars" data-template-name="$1">(inline script tag in HTML files using the Ember recommendeddata-template-nameattribute)x-id→<script type="text/x-handlebars-template" id="$1">(inline script tag in HTML files using the legacyidattribute)
Since (as of February 2017) the syntax definitions in this repository are driving the highlights on Github and in Visual Studio Code, it's fair game to open issues related to either of these 😺
It's a great JavaScript templating engine, based on Mustache, but amongst others adding the ability to precompile templates and to create custom helpers.
Official website: handlebarsjs.com
Get it through Sublime Package Control.
If you haven't used it yet, just install it from the link above and then:
- Press Shift + Cmd + P (OS X) or Shift + Ctrl + P (Windows)
- Type
install, to bring up thePackage Control: Install Packageoption, and press Enter - Look for
Handlebars, and press Enter to install it. - Choose
Handlebarsin the bottom right corner with one of your template files open (or in case you have inline templates use Handlebars instead of HTML, it's gracefully extending it so you shouldn't lose anything) - Profit
Package Control will also auto-update the package from this point on!
- Open Preferences > Install
- Type
Handlebarsinto the search field - Click the Install button
- Disable the core
language-mustachepackage so that it doesn't prevent this package to be used automatically with the supported file extensions
Problem: when closing an HTML tag, the tag name doesn't get auto-completed after typing / (or when using the Cmd + Alt + . (OS X) shortcut anywhere), even though this is the default behaviour with the HTML package.
Solution: installing the Tag package re-instates these functionalities and seems to be working well with this one.
Sublime: HTML tag pair doesn't get highlighted (#48)
Problem: moving the cursor over an HTML tag doesn't highlight its pair.
Solution: installing the BracketHighlighter package nicely solves the problem and adds much more powerful bracket matching than the built-in one.
Sublime: Expand selection to tag doesn't work (#47)
Problem: Expanding selection to tag doesn't work (Sublime command: expand_selection {"to": "tag"}).
Solution: if you install the Emmet package you can use the Match Tag Pair functionality by pressing Ctrl + D (OS X) or Ctrl + Shift + A (Windows).
Sublime: .sublime-build in the build system menu (#73)
Problem: a useless and confusing item named .sublime-build is added to the build system menu. This is because the package internally uses a custom build configuration to be able to target both Atom and Sublime and this gets exposed. Though it's only needed for development, Sublime doesn't seem to offer an option to hide this as the package gets installed.
Solution: delete the file from the package by running zip -d Handlebars.sublime-package ".sublime-build" in the folder it's installed or by any other means.
I've recently stopped heavily using Handlebars at my day job and became a father, so any contributions are more than welcome! I'm still using Github so will make sure to keep on being responsive on issues and pull requests.
There are some sample templates in test/ folder. It's possible to see the different supported and yet to be implemented use cases there.
If you want to work on the package you should install PackageDev either from Github or from Package Control. With that you can edit the JSON version (grammars/Handlebars.json) and let it export the Plist (grammars/Handlebars.tmLanguage) with the ST Build System.
The nicest development setup I found so far is to have the package installed via Package Control and then symlinking the development Git repo to Sublime settings folder > Packages, which then overrides the installed one so you can toggle between them easily.
Another great trick I found out about recently is the Show scope name shortcut (Shift + Ctrl + P (OS X) or Shift + Ctrl + Alt + P (Windows)) which will display the language scope on the status bar based on where your cursor is. If you're getting tired of pressing all these keys all the time, there are a few brilliant packages which do this automatically like the more subtle ScopeAlways or the full on ScopeHunter – note: both need to be activated via the Command Palette.
Resources on ST / Textmate syntax definitions:
http://docs.sublimetext.info/en/latest/extensibility/syntaxdefs.html http://manual.macromates.com/en/language_grammars
To see what scope Atom detects under the keyboard cursor, press Option + Cmd + P.
To publish a new version to atom.io the command is: apm publish [<newversion> | major | minor | patch | build]
TODO: add contribution notes
TODO: add proper testing based on specs in https://github.com/atom/language-mustache and https://github.com/Sneagan/atom-handlebars
This package does not offer any Handlebars precompilation functionality to keep things simple, but you can use Guard (which is a file system watcher) and Guard-Steering (a Handlebars precompiler from yours truly) to have all templates precompiled as you save them.
There's also a Guard package for Sublime if you want integration, but I don't personally use this as I'm happy with Guard running in an iTerm window I can access from anywhere.
There are of course Node.js / Grunt / Gulp based compilers too (like this and this), but I haven't personally used any yet for precompilation.
Adapted from the great sublime-text-handlebars package by Nicholas Westlake.
Thanks a lot to all the generous contributors!
(The MIT License)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.