feat: drop meteor (the final step) - #1805
Conversation
|
Important Review skippedToo many files! This PR contains 237 files, which is 137 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (237)
You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
f1f7434 to
39e5367
Compare
About the Contributor
This pull request is posted on behalf of Superfly
This is part of a series of PRs aiming to replace meteor.
Type of Contribution
This is a: Feature / Code improvement
Current Behavior
We are using meteor for the core backend app of Sofie. While this does give us some free stuff that we utilise, it also acts as a bit of a vendor lock-in and limits flexibility
New Behavior
This is the final push of dropping meteor.
This builds upon #1803, #1786 #1789 #1785 #1783 #1782 and includes all their changes. This PR will be rebased and tidied as the others get merged. Some bits may be plucked out into the above PRs as some of it fixing incompatibilities between them as they get merged.
Following this, the 'meteor' app, is just another nodejs app. Everything we still use from meteor (mongo wrappers and ddp server) has been rewritten as code that we own.
This has all been lightly tested, but will likely want some more thorough testing as parts get merged to ensure it does all operate as expected.
I have opted to not move the 'meteor' app into the packages directory or merge the yarn workspaces into one yet. I suspect that both of these will introduce quite a few merge conflicts, so am saving these for once the rest of this is merged and they can be pushed through quickly to avoid staleness.
Testing
Affected areas
Time Frame
Other Information
Status