Meteor 3

[StorytellerCZ]

• all code transformed to async
• full Fibers removal
• updated all deps / dev deps in package.js to Meteor 3 compatible versions
• update CI to GitHub actions
• drop Travis CI
• update documentation
• check integration with fix for meteor version 3 #203

Releases

• alpha
• beta
• RC
• release

[dallman2]

Looks good to me. Very similar to the workarounds i was using locally. Please merge this

[acemtp]

Looks good., when will it be merged and a new package released?

[StorytellerCZ]

@acemtp thanks for the ping. We'll need to look into replacing Travis, but I will try to release a beta in a few moments.

[acemtp]

Awesome, I try to clean my local patched package to be full ready for meteor 3.

I'll test the beta version as soon as available.

[StorytellerCZ]

Published mizzao:user-status@2.0.0-beta.0

[StorytellerCZ]

TODO:

• Get tests running as part of GitHub actions
• Merge in onStartup add defer and default query #163

[acemtp]

I used it on my project, it works fine! thanks for the release

[StorytellerCZ]

Just need to update tests for async and we should be fine.

[diavrank]

Hope to test the beta version in the next few days

[wreiske]

Meteor-Community-Packages/meteor-timesync#60 (comment)

[StorytellerCZ]

@wreiske Published mizzao:user-status@2.0.0-rc.2 which should fix the issue.

[imongithubnow]

I don't understand why this great package is stuck here, also 2.0.0-rc.2 version don't works on Meteor 3, there are few points to fix to align the await/async features.
I'm sure I'm missing something but I don't understand what.

[StorytellerCZ]

@imongithubnow it is simple, I don't have the time. PRs welcome.

[imongithubnow]

@imongithubnow it is simple, I don't have the time. PRs welcome.

ok this make a sense... :-)
I'm surprised that only a few changes were needed to fix it, so I don't understand why they haven't been made. I'm definitely doing something wrong... even if it works with these.
Anyway, I'll try to make a PR, out of curiosity.

[StorytellerCZ]

@imongithubnow open the PR against this branch which will get it merged faster.

[jankapunkt]

@StorytellerCZ since we dont get a quick mtest fix I would opt to move this package to mocha and biome

[imongithubnow]

@imongithubnow open the PR against this branch which will get it merged faster.

@StorytellerCZ I'm new to GitHub (as you can see ;-) ), I submitted a PR, but it fails.
2 questions:

• Why does it fail ? It looks like a CI stack issue.
• Unfortunately, I committed my code, and the formatting isn't the same as the original. Is this a big problem ?
  Thank you.

[imongithubnow]

@imongithubnow open the PR against this branch which will get it merged faster.

@StorytellerCZ I'm new to GitHub (as you can see ;-) ), I submitted a PR, but it fails. 2 questions:

* Why does it fail ? It looks like a CI stack issue.

* Unfortunately, I committed my code, and the formatting isn't the same as the original. Is this a big problem ?
  Thank you.

I commit good formatting code fews days ago ;-)

[jankapunkt]

@imongithubnow where did you format your code? I don't see any changes here.
@StorytellerCZ should I continue this PR?

[imongithubnow]

@imongithubnow where did you format your code? I don't see any changes here. @StorytellerCZ should I continue this PR?

I did a force-pushed over my previous commit
#203

[imongithubnow]

I saw tests, obviously with Meteor version before 2.9 faileds by unsupported async/await for Nodejs, for others tests there are some troubles about Node TLS, I don't understand why.
Maybe need some more changes ?

[jankapunkt]

Yeah, some things are still missing, I am making a little roadmap in the PR description and will look forward to get this all fixed up by the end of this week.

[harryadel]

After releasing https://github.com/Meteor-Community-Packages/meteor-timesync/releases/tag/v1.0.0 I noticed it'd not be possible to maintain the duality of user-status so I decided to double down on 3.0 with 2.0.0-rc.4'.

Awaiting your take guys, if all is we good we can do a full release very soon. Good night! 😴