codesandbox / codesandbox/codesandbox-client

Angular sandbox throwing connection closed before message completed issue

Open
#8,132 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

🐛 bug report

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I agree to follow the Code of Conduct that this project
    adheres to.
  • I have searched the issue tracker for an issue that matches the one I want
    to file, without success.

Description of the problem

Angular example is not working. The UI is throwing below issue

connection closed before message completed

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

image
To Reproduce
  • Go to codesandbox dashboard
  • Create new starter app with angular as preset
  • Check UI view
Link to sandbox: link (optional)
Your Environment
Software Name/Version
Сodesandbox
Browser CHrome
Operating System Windows

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

Start by opening the linked sandbox and reproducing the failure through the Codesandbox dashboard with the Angular starter preset, using the reported Chrome and Windows environment. Trace where the UI reports “connection closed before message completed”; done means the Angular example loads successfully without that error.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.