codesandbox / codesandbox/codesandbox-client

Standard Angular template doesn't run after Export to zip

Open
#5,255 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Angular Sandbox Templates
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

Standard Angular template doesn't run properly after Export to zip. After npm start it throw the error:
ENOENT: no such file or directory, stat 'path\project_name\src\tsconfig.app.json'

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

We are using CodeSandbox for the examples in our product (js library). We have Angular examples and want to allow our users to download zip and make changes locally. Also, we have some cases for our development too.

To Reproduce
  • create sandbox based on the standard angular example
  • export it to zip
  • extract zip archive locally
  • go the new project folder
  • run npm install
  • run npm start
  • see the error: ENOENT: no such file or directory, stat 'path\project_name\src\tsconfig.app.json'
Link to sandbox: link (optional)

https://codesandbox.io/s/just-standard-angular-example-z78eo

Your Environment
Software Name/Version
Сodesandbox codesandbox.io
Browser Chrome the latest
Operating System Windows 10 64
Nodejs v.14.15.0

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 failure from the linked Angular sandbox by exporting it, extracting the archive, running npm install, and then npm start. Inspect the exported project around src/tsconfig.app.json; done means the extracted standard Angular project starts successfully without the ENOENT error.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, javascript, nodejs
Domain
frontend, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.