kennygoff / kennygoff.com

kennygoff.com

My personal website on the internet.

→ kennygoff.com

Stack

• 🛠️ Build with Remix & React
• 💅 Styled with Tailwind
• 🚀 Deployed on Netlify

Development

To install use npm:

npm install

To run a development build locally:

npm run dev

To run a production build:

npm run build

kennygoff.com's Issues

Add Remix Dev Tools

https://github.com/Code-Forge-Net/Remix-Dev-Tools

Upgrade to Remix v2.8 and enable Vite

• Upgrade to Remix v2.7 and v2.8
• Enable Vite
• Update Netlify build to use vite

Investigate performance issues with Remix + Vite + Netlify Functions

https://answers.netlify.com/t/performance-issues-with-remix-vite-netlify-functions/113944
https://answers.netlify.com/t/remix-very-slow/115440/2

Revisit `remix dev --manual` when HMR issue is fixed

Originally posted by @pcattori in remix-run/remix#7466 (comment)

There's a couple different issues being conflated in this thread. Here are my current thoughts for disentangling them:

Issue 1: remix dev without --manual

If you are not using the -c flag for a custom server, there should be no reason not to use the --manual flag as it provides better DX anyway. remix dev without --manual should work too; if it doesn't currently, that's a bug. But in any case, I'd recommend just using remix dev --manual:

- remix dev
+ remix dev --manual

If you are using the -c flag for a custom server, check out our docs for manual mode.

Issue 2: wrangler + HMR

HMR seems to only work with wrangler <= 3.8.0 . Unsure if this is a bug in newer wrangler versions or (more likely) a race condition that is only prevalent for wrangler 3.9+. These sort of "file access" race conditions are only possible because we are coordinating the app server and the dev server via file writes (i.e. writing the server build to disk).

The principled solution is to not rely on files at all for coordination, which is exactly what Vite does. In fact, solving this type of race condition is exactly what first motivated me to look into Vite.

So in all likelihood, the workaround will be to stay on wrangler <= 3.8 until Vite (w/ CloudFlare support) is stabilized. Which is literally the thing I'm working on now. No promises on exact date, but rest assured its actively being worked on.

Other issues

If you have issues other than the two I mentioned here, it'd be great to track those in separate GitHub issues with specifics for your particular issue so we can make sure to prioritize those fixes accordingly.

Remix v9.1 Single Fetch

New single fetch behavior and undici (see https://remix.run/docs/en/main/guides/single-fetch)

Investigate Netlify Edge not working

Currently builds fail locally with npm run build on branch netlify-edge

Migrate to ESLint v9

https://eslint.org/blog/2024/04/eslint-v9.0.0-released/

Investigate default handler in `entry.server.ts` delaying on prod

• Default entry.server.ts always delays on netlify
• Using netlify starter template version works
• Figure out of bot handler requests is needed

See:

• https://codedgeekery.com/blog/remix-react-18