codesandbox / codesandbox/codesandbox-client
Angular: Renaming the '.angular-cli.json' file to 'angular.json' breaks the official template
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
Renaming the '.angular-cli.json' (which is deprecated since Angular v6 - 2018.05) file to now standard 'angular.json' breaks the angular official template
How has this issue affected you? What are you trying to accomplish?
The fact that the Angular configuration file (angular.json) is not complying to the frameworks standard format leads to broken workspaces as soon as you have a more complex application. This limitation practically makes Codesandbox unusable for real life examples.
To Reproduce
- Create a standard Angular sandbox
- Rename '.angular-cli.json' to 'angular.json'
Link to sandbox: sandbox-with-renamed-config-file (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | |
| Browser | Chrome |
| Operating System | Mac |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the problem in the linked sandbox, keen-williamson-t6do5, using the listed steps to rename .angular-cli.json to angular.json. Trace how the official Angular template discovers and loads its configuration, then verify that a renamed angular.json supports the template without breaking more complex workspaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100