Skip to content

fix: update browserslist on install rather than on serve - #623

Open
joanise wants to merge 2 commits into
dev.ej/angular-22-stackfrom
dev.ej/update-browserslist-on-install
Open

joanise wants to merge 2 commits into
dev.ej/angular-22-stackfrom
dev.ej/update-browserslist-on-install

Conversation

@joanise

@joanise joanise commented Oct 7, 2026

Copy link
Copy Markdown
Member

PR Goal?

Having serve depend on update-browserslist can cause a race condition when you're using npx nx run-many because one process (update-browserslist) is changing packages while others (serve-es, serve-fr, serve web-component) are compiling from them.

Also, having serve depend on update-browerslist makes serve much slower on my Windows machine, because the latter can easily take a minute.

We want to automate it, yes, but Del and I agree that on install is a better time and place to automate it than on serve, and it's plently often enough to satisfy our requirements.

Fixes?

race condition in run-many, delay each time I serve

Feedback sought?

Mostly making sure it works on MacOS and solves the problem @marctessier observed testing #620.

Priority?

low

Tests added?

well tested by CI

How to test?

  • See if CI passes
  • See if our standard install/run-many works on a fresh setup

Confidence?

high

Version change?

nope

Having serve depend on update-browserslist can cause a race condition
when you're using npx nx run-many because one process (update-browserslist) is
changing packages while others (serve-es, serve-fr, serve web-component) are
compiling from them.

Also, having serve depend on update-browerslist makes serve much slower on my
Windows machine, because the latter can easily take a minute.

We want to automate it, yes, but Del and I agree that on install is a better
time and place to automate it than on serve, and it's plently often enough to
satisfy our requirements.
@joanise
joanise requested review from deltork and marctessier October 7, 2026 20:50
@joanise
joanise added this pull request to stack #621 October 7, 2026 20:50
@semanticdiff-com

semanticdiff-com Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Review changes with  SemanticDiff

Changed Files
File Status
  package.json  67% smaller
  .github/workflows/bundle.yml  0% smaller
  .github/workflows/deploy.yml  0% smaller
  .github/workflows/dev-preview.yml  0% smaller
  .github/workflows/pr-preview.yml  0% smaller
  .github/workflows/release.yml  0% smaller
  .github/workflows/windows-tests.yml  0% smaller
  package-lock.json  0% smaller
  packages/studio-web/project.json  0% smaller

@github-actions

github-actions Bot commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor
PR Preview Action v1.6.3

🚀 View preview at
https://ReadAlongs.github.io/Studio-Web/pr-preview/pr-623/

Built to branch gh-pages at 2026-10-08 15:55 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@deltork deltork left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a husky post-merge hook might be useful. Update happens after every merge

@joanise

joanise commented Oct 7, 2026

Copy link
Copy Markdown
Member Author

I don't see post-merge hooks in the Husky documentation, but I'm also not sure I really want that...

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants