Next.js 13 - App directory

[oBusk]

In the (very) long run, I think the new Next.js rouing structure with Server Components could have many benefits to the npm-diff app.

• Load diff page directly, with loaders for diff and bundlephobia/packagephobia, and show any as soon as we have it.

  Not sure how caching works here? We obviously don't want to re-diff on every load, so we still need that strong caching.

• Maybe avoid sending diff-viewer to the client completely.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
npm-diff	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 16, 2023 1:55pm

[oBusk]

This will probably have to wait.

• https://beta.nextjs.org/docs/styling/css-in-js
• Plans to support Next.js 13 - /app directory emotion-js/emotion#2928
• Compatibility with server-side Web API runtimes: Next.js Edge Runtime, Deno, Cloudflare Workers / Pages. emotion-js/emotion#2801

[oBusk]

Also getting problems with everyones bane of existance, node-gyp.

./node_modules/node-gyp/lib/Find-VisualStudio.cs
Module parse failed: Unexpected token (9:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| // This script needs to be compatible with PowerShell v2 to run on Windows 2008R2 and Windows 7.
| 
> using System;
| using System.Text;
| using System.Runtime.InteropServices;

Should try a fresh repo and see if this problem still happens. Maybe open issue

[oBusk]

Also getting problems with everyones bane of existance, node-gyp.

./node_modules/node-gyp/lib/Find-VisualStudio.cs
Module parse failed: Unexpected token (9:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| // This script needs to be compatible with PowerShell v2 to run on Windows 2008R2 and Windows 7.
| 
> using System;
| using System.Text;
| using System.Runtime.InteropServices;

Should try a fresh repo and see if this problem still happens. Maybe open issue

This was caused by trying to run the props of the about/api page in clientside code. Moved it back to pages and running it on server again fixed it.

[oBusk]

📝 Changed routes:

5 deleted routes:

• /[...parts]
• /about/api
• /about
• /api/[...parts]
• /

Commit 14d0b76 (https://npm-diff-qn8tq4dgc-obusk.vercel.app).