-
Notifications
You must be signed in to change notification settings - Fork 72
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
Lets modernize! #418
Lets modernize! #418
Conversation
Upgraded node-sass and sharp and added a flag to `yarn install`.
This also required a couple upgrades of gatsby-remark related dependencies.
It's using an old version of sharp that's breaking cross-platform builds.
gatsby-plugin-favicon is deprecated and was causing all sorts of sharp versioning issues, while the manifest plugin is 1st-party and comes with localization functionality. Also untangled the resulting sharp version issues. This is the first time in years this repo has built cleanly on my machine.
d3222e8
to
96dfe43
Compare
Preview uploaded to https://preview.tbtc.network/lets-modernize/. |
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.
Noting for reference: we should be using pnpm in general now, yarn is legacy. Not a blocker since this gets us closer anyway.
Question: why'd we sprout all these .it.md
s? Otherwise, lgtm.
The build did it for unknown reasons. I gave up and committed them 😫 |
If by modernize, of course, you actually mean upgrading the minimal number of dependencies to get a cross-platform build 🥲