-
-
Notifications
You must be signed in to change notification settings - Fork 539
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
feat: upgrade to masto.js v6 #2530
Conversation
|
✅ Deploy Preview for elk-docs canceled.
|
✅ Deploy Preview for elk-zone ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
generally LGTM
We need to review types and logic in service-worker (@patak-dev I've sent you private DM in discord) |
The line you shared in Discord seems ok after the upgrade as it is a direct call. It doesn't use masto. If you could check anyways that things looks good on the service-worker/pwa side after this PR, appreciated! |
@patak-dev it seems to be fine: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sw logic seems to be fine
Search is fixed now. Tests are failing because of a type error on |
Fixed this one by polyfilling I think we should be good to go now. |
Let's merge this one so we try it out in https://main.elk.zone |
Thanks for this upgrade. I can proceed #2301 with this new version. 👍🏻 |
Check out the migration guide to see what's new in masto.js v6
The new rest API is quite nice (most of the changes in the PR are related to it). And the way streaming works also changed significantly. As far as I can tell, everything is working as expected (except for search, see neet/masto.js#1018. Pushing the PR as a draft until the fixes for are available as a new release).