codesandbox / codesandbox/codesandbox-client

Node.js SSE Sandbox Shows Stale Server Response

Open
#4,807 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🤔 Improvement SSE
Dominant language
JavaScript
Stars
13.6k
Forks
2.4k
Avg merge
6d 19h
Merged PRs (30d)
2

Description

🐛 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: https://github.com/shikijs/shiki/pull/82#issuecomment-686182578

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 b0052520f
Browser Chrome 85.0.4183.83
Operating System macOS Catalina 10.15.6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the behavior using the linked CodeSandbox and the listed steps: move src/index.js to index.js, update package.json, and change the file content. Start by checking whether the sandbox still serves the old response after the entry-point changes; done means the root index.js response updates reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.