3dyuval / 3dyuval/nvim

Node.js DAP Debugging Configuration

Abierto
#16 1 comentario 0 reacciones 0 asignados Ver en GitHub
enhancement
Lenguaje dominante
Fennel
Estrellas
0
Forks
0
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

## 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

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.