Daeraxa

Welcome to a new Pulsar regular release!

This time we have a brand new API, a reduction in Pulsar's installed size, a fix for a really tricky and annoying bug, and some fixes from the community.

One annoying thing that software developers do is insist on writing in more than one language at once. Web developers are espeically obnoxious about this — routinely, for instance, putting CSS inside their HTML, or HTML inside their JavaScript, or CSS inside their HTML inside their JavaScript.

Code editors like Pulsar need to roll with this, so today we’ll talk about how the modern Tree-sitter system handles what we call injections.

This month we have a couple of really significant changes to how Pulsar works internally by creating a couple of new APIs that can be used throughout the application, a new package to help you run code directly within Pulsar and our usual community spotlight to say thank you to those community members contributing to Pulsar's development!

Last time we looked at Tree-sitter’s query system and showed how it can be used to make a syntax highlighting engine in Pulsar. But syntax highlighting is simply the most visible of the various tasks that a language package performs.

Today we’ll look at two other systems — indentation hinting and code folding — and I’ll explain how queries can be used to support each one.

Here we are with another Pulsar release, and this month we have quite a number of fixes and improvements. This time the focus has really been on bug fixes in order to improve the overall experience.

We have updates to PPM for newer toolchain compatibility, a new Autocomplete API, better error handling for a crash at launch with invalid config and a fix for PHP snippets.

Last time I laid out the case for why we chose to embrace TextMate-style scope names, even in newer Tree-sitter grammars. I set a difficult challenge for Pulsar: make it so that a Tree-sitter grammar can do anything a TextMate grammar can do.

Today, I'd like to show you the specific problems that we had to solve in order to pull that off.

This month we announce our new "Pulsar Cooperative" initiative, showcase work being done to modernize the PPM codebase, introduce the new Shields.io badges for the Pulsar Package Repository, show off the new Pulsar integration in GitHub Desktop and talk about an issue we had with signing our macOS binaries.

In the last post, I tried to explain why the new Tree-sitter integration was worth writing about in the first place: because we needed to integrate it into a system defined by TextMate grammars, and we had to solve some challenging problems along the way.

Today I’ll try to illustrate what that system looks like and why it’s important.

The last few releases of Pulsar have been bragging about a feature that arguably isn’t even new: our experimental “modern” Tree-sitter implementation. You might’ve read that phrase a few times now without fully understanding what it means, and an explanation is long overdue.

This is the first of a series of articles about Pulsar’s ongoing project to migrate its Tree-sitter implementation to a more modern version. Read this first installment now on the Pulsar Blog

Our next release has arrived, and we are excited to share all the changes we have been making over the last month. We have a smorgasbord of bug fixes and QoL improvements.

We have completely overhauled our CI, converted the last of our CoffeeScript, removed the defunct "autoUpdate" API, improved our "about" package, squashed a bunch of bugs and even found ways to reduce our cloud costs!

A look into the significant ways that Pulsar's CI has recently changed. The why and how behind what happened.

Check out the latest community update on the Pulsar Blog!

In store for you this month we have some massive changes to our CI process, some good news for Windows Chocolatey users, a new option for Pulsar's title bar, some improvements to our ppm unpublish command and work on a brand new utility to help clean up elements of a Pulsar installation.