3dyuval / 3dyuval/nvim

Node.js DAP Debugging Configuration

Offen
#16 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
enhancement
Vorherrschende Sprache
Fennel
Sterne
0
Forks
0
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

## Issue Description
Current nvim-dap configuration for Node.js debugging is broken with RPC errors:
- `attempt to call method 'tostring' (a nil value)` in rpc.lua:23
- js-debug-adapter exits with code 1
- Mixed adapter configurations causing conflicts

## Current State
- Chrome debugging works properly
- Node.js debugging fails completely
- Configuration mixes node2 and pwa-node adapters incorrectly

## Requirements
1. Implement robust Node.js debugging with js-debug-adapter
2. Support TypeScript debugging with ts-node
3. Maintain existing Chrome debugging functionality
4. Follow Graphite keymap conventions (no hjkl)
5. Add proper error handling and logging

## Acceptance Criteria
- [ ] Single file Node.js debugging works
- [ ] TypeScript debugging with source maps
- [ ] Process attachment debugging
- [ ] launch.json compatibility
- [ ] Proper adapter configuration without RPC errors
- [ ] Test with headless Neovim as per AGENTS.md

## Technical Notes
Consider using proven configuration from nikolovlazar/dotfiles with:
- microsoft/vscode-js-debug adapter
- nvim-dap-vscode-js wrapper
- Proper build automation

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.