🚀 Introducing @a4xrbj1/meteor-desktop: A Modernized Fork

announce
1

Hi Meteor community! I’ve created and published an actively maintained fork of the Meteor desktop package with significant modernization updates.

What’s New?

@a4xrbj1/meteor-desktop brings the following improvements to the original package:

:white_check_mark: Updated Dependencies (13+ packages modernized)

  • Node.js requirement aligned to >=22.22.0 (matching current MeteorJS standards)
  • @electron/asar: 3.2.10 → 4.0.1
  • del: 6.1.1 → 8.0.1
  • node-fetch: 2.7.0 → 3.3.2
  • isbinaryfile: 3.0.3 → 5.0.0
  • rimraf: 6.1.2 → 6.1.3
  • And more…

:white_check_mark: Security Hardened

  • Removed deprecated packages (electron-packager, lodash.get, etc.)
  • Replaced deprecated packages with modern alternatives (@electron/packager)
  • All Trivy security scans passing with zero new vulnerabilities
  • Dev dependencies audited and cleaned

:white_check_mark: Build & Quality

  • Updated ESLint to support modern JavaScript syntax
  • Modernized Babel configuration
  • Successfully compiles all 20 source files
  • Chai testing ecosystem updated for modern assertions

Migration

To use the fork in your Meteor desktop projects, update your package.json:

Or if using GitHub for development:

Repository

:link: GitHub: https://github.com/a4xrbj1/meteor-desktop

The fork maintains full API compatibility with the original while providing modern, secure, and actively maintained codebase for building Electron-powered Meteor applications.

Happy building! :tada:

11 Likes
2


Guess I will have to deliver on my promise to bring back Meteor Toys

Dude thank you so much!!!

1 Like
3

It looks like every time I come back to the forum I see so many great news! Thank you very much Andreas!

4

Happy to help. This package is instrumental to our users app, hence I will keep updating it to stay on the newest ElectronJS versions and also make sure that we’re not having outdated dependencies.

However, I won’t support older versions of Meteor. For that use case the “old” repo is the correct one.

2 Likes
5

Looks great! I don’t have time to put into the electron repo. @a4xrbj1 do you want to take it over?

1 Like
6

Not really, I have my fork. To me, there’s no purpose for it, I’ve done already all the work and while not everyone will agree with my restrictions to use the latest MeteorJS version with my fork, that’s the best way going forward for me to ensure this package isn’t falling behind the latest Meteor versions or ElectronJS.

2 Likes