RicoSuter/aurelia-bs

Refresh F5 does not reflect changes in demo app

Open

#2 opened on Oct 13, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (2 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (7 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

  1. npm start
  2. Visit in browser
  3. Change code (TS file)
  4. Hit F5 in browser => No changes in browser
  5. Hit F5 a second time => Changes are now reflected

Contributor guide

Research direction
Check the Aurelia hot reload configuration and bundle settings. The first F5 may trigger a rebuild without a reload, while the second F5 picks up changes. Inspect the npm start script and bundler setup.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75