Skip to content

Add blog post about PulsarNext #307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

savetheclocktower
Copy link
Contributor

This is a blog post explaining why releases have slowed down, and what our plans are for the Electron upgrade. It also asks for more help testing PulsarNext and includes some basic instructions for getting it running and reporting any issues that may arise.

There are two things I'd love to get addressed before this goes out, but neither one of them is strictly necessary. They're both related to the packages that will be affected by the PulsarNext upgrade:

  • There's a known issue with x-terminal-reloaded where it fails to install if you don't have npx on your PATH. I've opened a PR to fix the issue.
  • I know we have a great replacement for the hydrogen package called hydron, but as far as I can tell it still has to be installed directly from GitHub, and the working version is on a branch other than main. Ideally, @mauricioszabo can publish it to the package repo soon; but if not, then perhaps he can give me straightforward installation instructions that I can include in the blog post.

Copy link
Member

@DeeDeeG DeeDeeG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me. I will hold off Approving to give others a chance to look at it as well, and integrate any updates to the stuff about Hydrogen/Hydron/etc. per recent discussion on Discord.

Thanks for working on all this stuff!

@savetheclocktower
Copy link
Contributor Author

Addressed feedback. Thanks for the review!


### Be the exact thing we need right now

If you’re a unicorn that loves Pulsar, has free time to contribute, and knows a lot about C++ and Node bindings …please reach out!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably give them some direction on where-best to reach out to

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point; I'll update this in an hour or so when I'm not on a bus.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added more explicit guidance for each of these options. Thanks!

Copy link
Member

@DeeDeeG DeeDeeG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blog post is go

@DeeDeeG DeeDeeG merged commit 11f5068 into pulsar-edit:main Jul 2, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants