Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Npm and Amber watch seem to hold on to old data. #475

Closed
IanEarley opened this issue Jan 3, 2018 · 2 comments
Closed

Npm and Amber watch seem to hold on to old data. #475

IanEarley opened this issue Jan 3, 2018 · 2 comments

Comments

@IanEarley
Copy link

Description

Npm and Amber watch seem to hold on to old data.
Changes are not reflected upon refresh of page.

Steps to Reproduce

  1. Run amber w
  2. make a change to project
  3. attempt to refresh the page.

Expected behavior: Content updates to show changes

Actual behavior: No changes rendered (note: terminating amber watch and refreshing the page still renders server info in terminal)

Reproduces how often: 90%

Versions

Amber Version - v0.6.0
Crystal Version - 0.24.1

OS - Gnome version 3.26.2

Additional Information

running with crystal on different port is a way around this for now.
@elorest
Copy link
Member

elorest commented Jan 3, 2018

Seems to be related in someway to NPM. I can kill all crystal/amber processes and it still renders code to my browser.

@eliasjpr
Copy link
Contributor

Somehow addressed with #457

@elorest elorest mentioned this issue Jan 14, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@elorest @eliasjpr @IanEarley