eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
Debug an Angular application in a Vagrant container
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
Hello,
TL;DR: How do I setup debug for an angular application inside a Vagrant container ? all debug instructions I could found presumed non-containerized use. Has someone been able to debug inside a container ?
Long story:
I'm using WWD for some time now and like it a lot. But I've never been able to setup debug correctly. It really didn't matter much because console.log and alerts were enough until now.
But recently I had a bug on the keycloak enabled app-init of my application. So the app just reloaded everytime and I had to excessively use alerts with JSON.stringify to debug it. This is rather inefficient.
So this made me feel it's about time for me to setup debug correcty.
I've seens these instructions:
https://github.com/eclipse/wildwebdeveloper/issues/661
https://github.com/eclipse/wildwebdeveloper/blob/master/TIPS_and_FAQ.md
https://github.com/eclipse/wildwebdeveloper/issues/566
https://github.com/eclipse/wildwebdeveloper/issues/111
I've also seen this question on SO:
https://stackoverflow.com/questions/25617323/can-i-debug-angularjs-and-typescript-in-eclipse
But as I said all of them presume host, non-containerised usage.
Any help appreciated. Thanks.
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 with TIPS_and_FAQ.md and the linked issues #661, #566, and #111, then compare their host-based debugging guidance with the Vagrant-container scenario described here. Done means providing or documenting a verified way to debug an Angular application inside a Vagrant container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular
- Domain
- developer-experience
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100