Update documentation with "how to debug"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Describe the feature
Nuxt now has a page called "Debugging" (https://nuxt.com/docs/guide/going-further/debugging#example-jetbrains-ides-debug-configuration)
It would be nice to add a support page for nitro.
Both https://github.com/unjs/nitro/discussions/2141 and https://github.com/unjs/nitro/discussions/2057 already mention how to do this for vscode and jetbrains.
I would be able to add an initial page if helped in what to add to the page and where to put it.
Additional information
- Would you be willing to help implement this feature?
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 reading the Nuxt Debugging page and discussions 2141 and 2057 for the existing VSCode and JetBrains guidance. Identify where Nitro documentation pages are organized, then add a support page covering those debug configurations; it is done when the page is published in the appropriate documentation section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100