Skip to main content
Back to Extensions Directory
coc.nvim fallback icon

coc-spring-dashboard

asmodeus812

Spring Boot dashboard for coc.nvim

Installation CommandVim prompt
:CocInstall coc-spring-dashboard
GitHub owner
asmodeus812
Version
v0.4.3
Requirements
coc ^0.0.82
License
MIT
Repository
GitHub
npm latest published 2026-11-21Registry summary

Published Package Summary

coc-spring-dashboard

Spring Boot dashboard for coc.nvim: tree views of the Spring Boot apps of the workspace, their beans, endpoint mappings, properties and memory, and signs on bean definitions and request mappings in the code.

It is a port of microsoft/vscode-spring-boot-dashboard (MIT). See NOTICE and LICENSE.

Using it inside Neovim is described in the help page: :help coc-spring-dashboard.

Requirements

  • coc-java and coc-springboot, installed and active (declared as extension dependencies). The dashboard gets all of its data through them and waits for their servers to start, the Java server until it has imported the projects; until then it says "Java server starting" or "Spring Boot server not running".

  • For live data (running state, live beans and mappings, properties, memory), a running app with spring-boot-starter-actuator on its classpath, started with these JVM arguments (the dashboard adds them to the apps it starts, from the vmArgs of spring.dashboard.launch.defaults):

    -Dspring.jmx.enabled=true -Dmanagement.endpoints.jmx.exposure.include=*
    -Dmanagement.endpoint.env.show-values=ALWAYS
    
  • Apps started by the dashboard connect by their pid and need no setting. Other apps connect through Attach to a remote app (spring-boot-dashboard.app.remote.attach), or through coc-springboot's springboot.app.connect picker, which offers the apps on your machine only with this coc-springboot setting in coc-settings.json (see :help coc-springboot-local-apps):

    "boot-java.live-information.all-local-java-processes": true
    
  • For Debug, Attach debugger and the debug half of Attach to a remote app, nvim-dap in Neovim or vimspector in Vim and Neovim. Run needs no debugger.

Run, Debug and Stop are done by the dashboard: it opens a launch panel (profiles, server port, logging, JVM options, program arguments and environment, remembered per app), starts the JVM in a tab per app, the dashboard of the app (Beans, Mappings, Properties and Memory over the terminal), and stops it with SIGTERM and then SIGKILL. The JMX arguments above are added for you for apps it starts.

Installation

:CocInstall coc-spring-dashboard

Or build a checkout and add its folder to the runtimepath with your plugin manager:

npm ci
npm run build

Troubleshooting

  • Failed requests to the Spring language server are logged to the output channel "Spring Dashboard": :CocCommand workspace.showOutput Spring Dashboard.
  • Jumps from the views and nvim-dap stops open in the source window of the app: the window Run, Debug or Attach was started from, or the first file window of its tab; without one, or outside an app tab, in a float.
  • No trees, or a warning that coc-springboot or coc-java is not active: check :CocList extensions and open a Java file of the project.
  • An app stays ○ stopped while it runs: check the actuator dependency, the JVM arguments above, then run :CocCommand spring-boot-dashboard.livedata.refresh.
  • Every message the dashboard shows is explained in :help coc-spring-dashboard-messages.

Development

npm ci
npm run build
npm run typecheck
Read the complete README
  • Spring Boot dashboard for coc.nvim
Activation Events
  • onLanguage:java
Developer Resources

Want to build, test, or contribute to coc.nvim extensions? Explore our official SDK and testing toolkits.

Open Developer Guide

Version History

This published npm package does not include a history.md or changelog.md file. Browse its npm versions or repository releases for available release information.