Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[browser-esbuild] live-reload=false workflow is less convenient now

Open
#27,479 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
build-system, cli

Research direction

Start with the serve command's live-reload=false workflow and trace how browser requests behave while esbuild compiles changes. Reproduce the refresh sequence, then verify that a refresh waits for successful compilation or that compilation completion is surfaced in the browser console.

Written by the indexing model from the issue text.

Description

area: @angular-devkit/build-angular devkit/build-angular:dev-server freq1: low severity2: inconvenient type: bug/fix
Command

serve

Description

I often work with live-reload disabled. This is helpful when working on CSS changes, I can try things in browser and then make multiple edits in files before manually reloading.
It's also faster when working on a laptop.

Before esbuild:

  1. Make changes.
  2. Refresh page.
  3. Page reloads after new changes have been compiled.

With esbuild:

  1. Changes.
  2. Refresh.
  3. Page reloads immediately before changes have been compiled. Now I need to monitor terminal and reload the page after successful compilation.
Describe the solution you'd like

I was okay with the old behaviour where server wouldn't respond before successful compilation.

A less desired alternative would be to log Vite messages in browser's console, so that I can tell when compilation has finished there.

Describe alternatives you've considered

No response

Dominant language
TypeScript
Stars
27k
Forks
11.8k
Avg merge
16h 35m
Merged PRs (30d)
176

Contributor guide

Open the contributing guide

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 angular/angular-cli

All issues in angular/angular-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.