Great Scott! A new Pulsar release. Pulsar 1.108.0 is available now!

DaeraxaAugust 16, 2023
  • dev
  • release
About 4 min

Great Scott! A new Pulsar release. Pulsar 1.108.0 is available now!open in new window

What is new in 1.108.0?

Welcome to our latest Pulsar release! We have some really exciting new features this month that we can't wait to share.

To kick things off, we have a brand new core package, pulsar-updater. We recently featured this on our monthly Community updateopen in new window , but in case you missed it (or simply just want to read more about it), pulsar-updater is a new package designed to help notify users about new Pulsar releases and where they can get them. As always, we are open to feedback, especially when we have brand new functionality like this, so please let us know via any of our social channelsopen in new window if you have anything for us.

Next, we have yet more grammars for our modern Tree-sitter implementation. If you have missed any details on this, then you can read more on our blogopen in new window. The two new grammars in question are for Markdown and YAML. So what benefits does this give us? Well, for example, with Markdown, this provides significantly more accurate highlighting than the existing "Textmate" grammar; it provides HTML syntax highlighting as well as YAML frontmatter support (a common addition to Markdown documents these days, particularly for static site generators), and it allows us to clean up some of the scope names to suit a more conventional approach to naming. All these features should provide a much better Markdown writing experience in Pulsar and allow us to easily keep it up to date with anything new we might want to add in the future.

On the topic of Markdown we also have a rather large update to our markdown-preview package, which provides a window to display the rendered output of your Markdown documents. The big change here is the syntax highlighting displayed within code blocks specified via a "language identifier". The list of these supported identifiers was rather out of date, and the world had moved on around it, so the decision was made to bring this up to date with the behaviour that people expect from such functionality. We go into far more detail about this change in our Blog postopen in new window so have a read of that if you want to know the full details about this change.

Last, but definitely not least, we have finally begun the migration from apm to ppm. When we started the Pulsar project, one of the first things we did was rename the "Atom Package Manager" to the "Pulsar Package Manager" for obvious reasons. However, under the hood, you would still find apm binaries and files; this was particularly relevant for Windows users, for which there was no automatic PATH registration. The good news is that we have begun the transition to change them. For the time being, apm will remain alongside ppm until we can be sure we haven't hit any unforeseen issues.

And with that, we bring this to a close. As ever, a huge thank you to all of our community members and especially our donors, without whom this project just wouldn't be possible.

Until next time, happy coding, and see you amongst the stars!

  • The Pulsar Team


  • Restored ability for less files in packages to use inline JavaScript inside backticks.
  • Fixed a syntax highlighting issue inside the styleguide package.
  • Fixed an issue with rubygems timing out on ARM Linux workflow.
  • Rewrote Tree-sitter scope predicates to use #is? and #is-not? where applicable.
  • Ensure that project-specific setting overrides don't leak to the user's config file when the settings UI is visited.
  • Added a feature in markdown-preview that adds support for Linguist, Chroma, Rouge, and HighlightJS for language identifiers in fenced code blocks.
  • Fixed the TextMate language-toml grammar to properly support whitespace where-ever it may appear.
  • Added a Tree-Sitter grammar for YAML files.
  • Added a new core package pulsar-updater to help users update Pulsar.
  • Added ppm and ppm.cmd binaries/launchers within ppm. This allows easier integration of correctly named binaries on more systems in more contexts (especially Windows). Existing apm and apm.cmd binaries/launchers are still there for the time being.
  • Added a modern Tree-Sitter grammar for Markdown files.