Error: No such version [email protected] and [email protected]

[JefeAnde]

Describe the bug

Fails on Step 4: npm run desktop -- init

While adding package communitypackages:meteor-desktop-watcher@=3.2.1:
error: no such version communitypackages:[email protected]

While adding package communitypackages:meteor-desktop-bundler@=3.2.1:
error: no such version communitypackages:[email protected]

To Reproduce

Walk through the steps in the Readme.

1. cd /your/meteor/app
2. meteor npm install --save-dev @meteor-community/meteor-desktop
3. meteor add-platform ios # or android
4. npm run desktop -- init

Fails on Step 4: npm run desktop -- init

It appears it is using the Meteor Desktop Package version (3.2.1) to add the same specified version of

• communitypackages:meteor-desktop-watcher
• communitypackages:meteor-desktop-bundler

https://packosphere.com/communitypackages/meteor-desktop-bundler shows version 3.2.0
https://packosphere.com/communitypackages/meteor-desktop-watcher shows version 3.2.0

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee your issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

[minhna]

I had the same problem.

[StorytellerCZ]

Published v3.3.0 of everything. Please check if that helps.

[awatson1978]

I gave it another try, after clearing out the node_modules folder and re-installing using the @meteor-community/meteor-desktop. Managed to get through the npm run desktop -- init command and past the no such version errors, and it actually seems to be trying to build the desktop executable. New errors are the following:

Which seem to be related to issues in #41