vercel[bot]
commented
2 years ago This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/theobr/init-tips/C88hgBafq96N8amp8uqJkr5Qo6W1
✅ Preview: https://init-tips-git-fork-jasondocton-main-theobr.vercel.app
t3dotgg
Hey Theo!! I've been making some tweaks to the init.tips repo :D. I noticed the lighthouse score for performance was 66, but I've got that back up to 96-99. Can't seem to figure out what is stopping it from a 100 score, because the Largest Contentful Paint is just a
with nothing special about it. Could be the case that doing an import of strings into an array would fix this for the /other page.
I've got the accessibility score up. The clipboard can now be tab targeted and copied with the keyboard or voice command. External links all open in a separate window to increase time spent on the page and improve SEO. Alongside the SEO edits, I removed the head.tsx component, which was bringing performance down. Instead, most of the SEO is built into a _document.tsx file. There is an eslint-ignore at the top of that file, but only because Next's lint settings require the _document to be .js, because they never updated their lint docs to acknowledge .tsx. Since the only SEO change across pages was the Title on /other, I've imported the next/head to update the titles. Next Head specifically has a key set to avoid content update issues.
Updated .vs settings to remove yellow lines on Tailwind stuff and included Tailwind Intellisense functionality.
Updated Tailwind and its related plugins, updated the purge settings, removed mode: "jit" since it's on by default now, and removed darkMode since "false" isn't needed.
Updated Next and its deps to avoid the minor exploit possible with Next 11-12.01.
Enabled Rust Minification and dropped target: "serverless", since Next 12+ manages the features of target: "serverless."
Moved Next/types/global to the next.config, as per recommendation from Next.
Style wise, I updated to the latest css reset recommendations, added reduced motion if a browser/desktop has specifically set reduced-motion. Applied minor fixes to avoid clipping through or otherwise causing issues with iOS's bottom bar.
Also added a _middleware.tsx page, which meets the A+ standard for content security policy recommendations by Mozilla and Google. It includes script allowance for Plausible, so full tracking will work.