Extremely long time to first page interactivity in dev

Open
#3,821 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
deno, tailwindcss, typescript
Domain
devtools

Research direction

Start with the deno task dev entry point and trace the first request that keeps vite.js at full CPU until the page becomes interactive. The report names Tailwind CSS, DaisyUI, Hono, Zod, and Zod OpenAPI as added modules; investigate how they affect startup and route changes. Done means identifying and fixing the cause of the multi-minute delay, with first load and hot reloading working normally.

Written by the indexing model from the issue text.

Description

Starting with deno task dev will, upon first request to the server, take multiple minutes until the page is shown and interactive. During that time, deno run --ext=js -A ... vite.js is constantly at 100% CPU usage on one processor core. After that is done, the app and hot reloading work mostly normal, but some changes (e.g. new routes) will restart that process.

The project was created with deno run -Ar jsr:@fresh/init. We then added the following modules:

  • tailwindcss
  • daisyui
  • hono
  • zod & zod-openapi
Dominant language
TypeScript
Stars
13.8k
Forks
757
Avg merge
3m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from freshframework/fresh

All issues in freshframework/fresh

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.