Daeraxa

While a smaller release this time around, v1.119.0 still manages to pack a punch.

For macOS, we've gone to great lengths to ensure Pulsar should build just fine on macOS 13+, while our Linux users get greater compatibility for DevTools on various platforms. For our programmers, there's been more of the constant incremental improvements to various languages' built-in syntax highlighting and code folding this time around, with a focus on PHP, Python, Javascript, Typescript, Shell script, and C.

As always thanks a ton to all of those that support the project and keep it moving forward, we appreciate you all, and look forward to seeing you amongst the stars.

Get your grills ready, Pulsar v1.118.0 is cooking with gas! With lots of love to syntax highlighting, along with a zesty sprinkling of features and fixes. We've got Tree-sitter fixes and improvements from query tests, better documentation of our Tree-sitter usage, an updated PHP parser, and loads of improvements to Clojure, there should be a little something for everyone. But of course feel free to dive into the changelog for further details.

A week later than you’re accustomed to — but worth the wait! Pulsar 1.115.0 is available now!

Last month’s 1.114.0 release was full of fixes related to the recent migration to modern Tree-sitter. This month’s release is much smaller, but still dominated by Tree-sitter fixes affecting syntax highlighting, code folding, and indentation.

Welcome to a brand new Pulsar release!This release features a lot of updates and fixes for our modern Tree-sitter implementation, an assorted bag of bug fixes and some new features to introduce, such as restoring compatibility with older Linux distributions and a new ppm command.

Last month was our biggest update to Pulsar we have had in quite a while, so in this blog we will be addressing some of the issues people have seen and what you can expect in terms of fixes and updates. Outside of that, we have some big changes to the Pulsar Package Registry backend that give (and document) a bunch of new filters and endpoints to the API, as well as a reminder for @maurício szabo's blog post detailing our biggest hurdle: the road to modern versions of Electron.

In the beginning, Atom appeared. It created an API to make packages, but together with this API, it also allowed authors to use web APIs together with node.js packages, modules (including "native modules" - more on that later) and, finally, a special API that was used to communicate between the "main module" and the "browser part".

That last part, eventually, split from Atom and became Electron. And for a while, the Atom development was tied to the Electron one, meaning that an update on Atom usually meant an update on Electron, and vice-versa.

Unfortunately, that wasn't the case for a long time...

We’ve been telling a series of stories about all the different ways that Tree-sitter can improve the editing experience in Pulsar. Today’s story about symbols-view starts a bit slowly, but it’s got a great ending: the addition of a major new feature to Pulsar 1.113.

Welcome to the release of Pulsar 1.113.0, our first release of 2024. For this release we have enabled our modern Tree-sitter implementation by default, a new Tree-sitter PHP grammar, a huge update to our 'symbols-view' package, a bunch of bug fixes and an issue where we banish 😡 to the Netherrealm.

Welcome to our first community update of 2024! We have a reminder about our upcoming tree-sitter change, a resolution to our annoying website issues, a brand new PPR API endpoint so you can find packages by your favourite authors, a statement on our commitment to our long-term projects and a very special new year community spotlight.

Welcome to our 12th regular release! It has been exactly a year since we put out our first tagged release and development continues. This month we have some new soft-wrapping options, some long overdue updates to PPM, improvements to our "GitHub" package, a new fuzzyMatcher API and our usual slew of bug fixes.

This month we have a big update on our plans to move to a new version of electron and what that might mean for our releases, some better error handling on our package website and our usual community spotlight to say thank you to those community members contributing to Pulsar's development!