Pinafore v1.0.0 (1/3) Show more
Pinafore has hit v1.0.0! Rather than a momentous occasion, though, this is more to communicate a breaking change for those who self-host Pinafore (ala semantic versioning: https://semver.org). But there are also some new features and bugfixes!
⚠️ Breaking change ⚠️
Pinafore now uses yarn instead of npm. If you self-host, learn how to update: https://github.com/nolanlawson/pinafore/blob/master/BREAKING_CHANGES.md#100
Pinafore v1.0.0 (2/3) Show more
Pinafore v1.0.0 (3/3) Show more
If you've set "reduce motion in UI animations," then all smooth-scrolling will now be disabled (e.g. tapping the nav bar to scroll to the top, keyboard shortcuts to scroll through toots, the image carousel, etc.).
If you've set "Disable tappable area on entire toot," then the cursor will no longer be a hand when you hover over toots.
Thanks, and enjoy Pinafore v1.0.0!
Full release notes: https://github.com/nolanlawson/pinafore/releases
@pinafore: Congrats on release 1.0!
@nightpool Believe me, I was not gonna switch to yarn unless I needed to. I prefer using out-of-the-box tools wherever possible.
The problem is that there's a bug in Webpack (https://github.com/webpack/webpack/issues/8656) which is apparently caused by an npm bug (https://npm.community/t/packages-with-peerdependencies-are-incorrectly-hoisted/4794).
Switching to yarn fixes the bug, as well as making my CI tests faster because I have to use yarn to run Mastodon anyway. Plus I no longer have weird merge conflicts over package-lock.json (Yarn's lockfile is more sensible).
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!