feat: Add script to get npm package data

[lachlancollins]

🎯 Changes

This PR adds auto-fetching package data from npm. The scripts/updateNpm.js script runs the npm CLI in parallel to get info listed here. For now, I've set it to save the latest release date, latest version (useful to show how up-to-date the info is and for other tools such as publint), and svelte peerDep (if available).

For now, the latest version and date are added to the package card (if it exists). The date is rendered as a relative date using dayjs. I've moved the repo button from the bottom-left to the top-right of the card (this was the most space-efficient arrangement of stars, repo and date I could pick).

Before:

After:

✅ Checklist

• I have given my PR a descriptive title
• I have run pnpm run lint locally on my changes

[netlify]

✅ Deploy Preview for sveltesociety-preview ready!

Name	Link
🔨 Latest commit	4853733
🔍 Latest deploy log	https://app.netlify.com/sites/sveltesociety-preview/deploys/657f6af9d92ffc00089ea219
😎 Deploy Preview	https://deploy-preview-499--sveltesociety-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[MacFJA]

I'm not sure about creating a file by data type 🤔

If the data were to be updated separately, it could make sens, but here everything is updated together at each run

[lachlancollins]

I'm not sure about creating a file by data type 🤔

If the data were to be updated separately, it could make sens, but here everything is updated together at each run

Yep for sure, definitely makes sense - I started off just with a versions.json then it grew!

Which one of these do you think would be better?

"versions": {
		"super-sitemap": "0.14.11",
		"svelte-scrollactive": "0.0.9",
		...

"super-sitemap": {
		"version": "0.14.11",
		"date": "2023-11-18T20:28:44.230Z",
		...

[MacFJA]

I would reduce the font size of the date.

It's a bit too "in your face" right now. It has the same font-size as the description, making it as important as the description.

Also, I don't find use <code> revelant here, it's a "none-technical" information nor a number