Thanks to visit codestin.com
Credit goes to github.com

Skip to content

The esbuild called by Kolosal didn't close. #20

@madebyaris

Description

@madebyaris

Problem

I'm noticing that the npm run dev or any stuff like that, didn't close when we quit the kolosal, thus, it make unnecassary bloated resource:

Image

On my case, it called 3-4 npm run dev, and they are also using 4 ports.

I'm noticing it's also happen on the IDE built-in VSCODE.

solutions

We should close all the npm run dev terminal that running because we spawn it, when we close our kolosal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions