NativeScript / NativeScript/nativescript-cli
Show a number for the code line in command line
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 204
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
When getting an error, it is not everytime clear where it comes from. For example, when using Vue.js, you am getting an error message which looks like this (note the line of code next to vue.js:)
vue.js:597 [Vue warn]: Error in created hook: "TypeError: ... is not a function"
found in
---> <StageExecs>
In Nativescript / nativescript-vue you get an error message which looks like this:
JS: [Vue warn]: Error in created hook: "TypeError: Cannot read property '...' of undefined"
JS:
JS: found in
JS:
JS: ---> <IsRenovationFinishedField> at SomeFile.vue
But if you don't know the line of code it is very hard to find the error.
Describe the solution you'd like
Next to JS there should be a code line indicator
Describe alternatives you've considered
Additional context
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
The issue names no files, tests, or entry point. Start by tracing how the CLI formats JavaScript error output, then determine where the JS prefix and source locations are produced. Done means command-line errors include a usable code-line indicator next to JS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100