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.

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

Node.js SSE Sandbox Shows Stale Server Response #4807

Open
karlhorky opened this issue Sep 3, 2020 · 6 comments
Open

Node.js SSE Sandbox Shows Stale Server Response #4807

karlhorky opened this issue Sep 3, 2020 · 6 comments

Comments

@karlhorky
Copy link

🐛 bug report

Description of the problem

The sandbox below shows stale server response. The src/index.js file has been moved to index.js (and the main and start in the package.json file updated, including the nodemon src/index.js)

https://codesandbox.io/s/dark-glade-dq2t2?file=/index.js

Screen Shot 2020-09-03 at 10 38 31

Repro steps:

  1. Start a new Node.js sandbox
  2. Drag the src/index.js out of the src directory into the root
  3. Update the paths in the package.json in both main and start
  4. Change the content in the index.js file
  5. See stale content

How has this issue affected you? What are you trying to accomplish?

I want to have the index.js file in the root in a Node.js sandbox.

Trying to create a demo for Shiki: shikijs/shiki#82 (comment)

The errors are causing low confidence in the reproducibility and stability of the sandbox.

Link to sandbox: see above.

Your Environment

Software Name/Version
Сodesandbox b005252
Browser Chrome 85.0.4183.83
Operating System macOS Catalina 10.15.6
@lbogdan
Copy link
Contributor

lbogdan commented Sep 3, 2020

Hey @karlhorky ,

Did you restart the sandbox after you changed the start script in package.json?

image

@karlhorky
Copy link
Author

Nope, didn't try that.

However, I would suggest that this should happen automatically in case there is a change to the start, dev, or develop script.

Would that be feasible?

@github-actions
Copy link

github-actions bot commented Dec 4, 2020

This issue has automatically been marked stale because there has been no activity in a while. Please leave a comment if the issue has not been resolved, or if it is not stale for any other reason. After 2 weeks, this issue will automatically be closed, unless a comment is made or the stale label is removed.

@github-actions github-actions bot added the stale label Dec 4, 2020
@karlhorky
Copy link
Author

Not stale

@github-actions github-actions bot removed the stale label Dec 5, 2020
@github-actions
Copy link

github-actions bot commented Mar 5, 2021

This issue has automatically been marked stale because there has been no activity in a while. Please leave a comment if the issue has not been resolved, or if it is not stale for any other reason. After 2 weeks, this issue will automatically be closed, unless a comment is made or the stale label is removed.

@github-actions github-actions bot added the stale label Mar 5, 2021
@karlhorky
Copy link
Author

let's say not stale?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants