alsiola / pm2-explorer

Manage PM2 from within VSCode

PM2 Explorer README

View and interact with currently running PM2 processes within VSCode. This extension can be installed from within VSCode by searching for pm2 in the extensions view, or via the Visual Studio Marketplace

Features

Adds a PM2 Explorer view that lists current PM2 processes and important details about them. The list is updated at a configurable interval (default 1000ms).

Allows interaction with individual running processes:

• Start
• Stop
• Restart
• View Logs (in integrated terminal)

And with all running processes:

• Reload all
• View all logs
• Start all processes
• Stop all processes

Requirements

PM2 should be installed globally on your machine.

Extension Settings

The following configuration settings are provided by PM2 explorer:

// How frequently (in milliseconds) should the process list update
"pm2Explorer.refreshIntervalMs": 1000

Known Issues

No known issues

Release Notes

0.0.7

• Fix commands when tasks have whitespace
• Dependency vulnerability updates

0.0.6

• Restore accidentally removed container icon

0.0.5

• Re-publish broken CI deployment

0.0.4

• Improved process icons
• Configurable refresh interval
• Added start all and stop all commands
• Refactor and re-organisation

0.0.3

• Visual representation of process state

0.0.2

• Fix errors in readme
• Add logo

0.0.1

• Initial release of PM2 Explorer

pm2-explorer's Issues

Services with a space in the name don't show logs correctly

pm2-explorer doesn't quote service names, so showing the logs for a service doesn't work if there's spaces in the service name. Quoting the service name should be all that's needed.

Fixing process uptime

convert from ms to h:m:s
by get time now - process uptime
and then use this for convert to h:m:s

function msToTime(s) {
    
    function pad(n, z) {
        z = z || 2;
        return ('00' + n).slice(-z);
    }

    var ms = s % 1000;
    s = (s - ms) / 1000;
    var secs = s % 60;
    s = (s - secs) / 60;
    var mins = s % 60;
    var hrs = (s - mins) / 60;

    return pad(hrs) + ':' + pad(mins) + ':' + pad(secs);
}

from this

to this

*i fix it on my computer but i don't know the code ts sory :<
my fix file
pm2-explorer.zip

CI/Automation

Setup builds for develop and master branches.

• develop - dry run test/build, no publish
• master - test/build/publish

Test/build PRs

Make refresh interval configurable

Add a configuration contribution point with a refresh interval (seconds or milliseconds?), and use this in the PM2 class.

FR: make it configurable what to watch

You can start a PM2 process.

It is nice if it can start with the --watch options

Configurable display

Configurable display of data points (id, status, uptime, instances, memory, cpu, mode, unstable restarts etc.) - Let the users choose what they want to see but provide defaults.

Improve testing

Add some unit tests around key parts of the extension, with some integration/e2e tests where possible.

Create Contributing Guidelines

This should include instructions on how to run the extension locally in development, the branching strategy used by the project, how to raise issues etc.

It can included a basic code of conduct.

Filterable process list

Search for a process (filter tree list by PM2 process name)

Add logs options

Add options to delete, flush logs for a process and same for global actions

Provide Dockerfile for smoother CI/CD

Per #3 I think it would be prudent to provide a dockerfile to containerize the app and allow for smoother testing and deployment.

Make uptime human readable

Uptime should be shown in a human readable form rather than in milliseconds, e.g.

10 seconds
5 minutes
3 days

Refactoring and testing

Currently the code is functional but there poorly structured. The PM2 classes are responsible for both interacting with PM2 and displaying views - poor separation of concerns. There are several easy wins here, but it is also worth looking at other VSCode extensions and following any established conventions around program structure to make future collaboration easier.

There are currently no unit tests. These should probably focus on ensuring we correctly handle error conditions when PM2 is inaccessible or responds unexpectedly.

Highlight the row red when the process is in an errored state.

Get some nicer icons

There are currently icons that reflect the process state - online, stopped, errored and starting. They are not visually appealing, and do not follow a common theme.

Internationalisation

Ensure that all static strings are extracted, with a mechanism to change the currently displayed language.

Consider what languages should initially be supported, and how to get translations (ask for help, machine translations)

Add pm2 monit global action

Global action - Launch pm2 monit in the terminal