-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Comments
Hey @karlhorky , Did you restart the sandbox after you changed the |
Nope, didn't try that. However, I would suggest that this should happen automatically in case there is a change to the Would that be feasible? |
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. |
Not stale |
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. |
let's say not stale? |
🐛 bug report
Description of the problem
The sandbox below shows stale server response. The
src/index.js
file has been moved toindex.js
(and themain
andstart
in thepackage.json
file updated, including thenodemon src/index.js
)https://codesandbox.io/s/dark-glade-dq2t2?file=/index.js
Repro steps:
src/index.js
out of thesrc
directory into the rootpackage.json
in bothmain
andstart
index.js
fileHow 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
The text was updated successfully, but these errors were encountered: