PNPM shutdown

[alechka]

Hi! A have a pnpm app, configured with my aspire project like this:

var front = builder
    .AddPnpmApp("front", "../../../js/platform-frontend", "serve")
    .WithEnvironment("NODE_OPTIONS", "--no-experimental-require-module")
    .WithArgs("--port=4174")
    .WithHttpEndpoint(env: "VITE_PORT")
    .WithExternalHttpEndpoints();

Everytime when i am stopping AppHost, application is still running and consuming port. Am I doing something wrong or is it a bug?

OS: Ubuntu
Package versions:

<PackageReference Include="Aspire.Hosting.AppHost" Version="9.2.1" />
<PackageReference Include="Aspire.Hosting.MySql" Version="9.2.1" />
<PackageReference Include="CommunityToolkit.Aspire.Hosting.NodeJS.Extensions" Version="9.4.0" />

(this is first time I am submitting an issue to github, so sorry if i am doing something wrong)

[aaronpowell]

How does it report that the port is still in use? Are you seeing the running process in the process list or is it reporting differently?

[karolz-ms]

With Node apps I have seen the cases when the command that starts the app (npm run, or similar), creates a bunch of child processes and one of them eventually "detaches" itself from the parent process tree. Thus, when Aspire tries to stop the app, it does not "see" the child process that is holding the port anymore and can't stop it.

I would be curious how the process tree looks like once the app is running and what is the relationship of the process that holds the port and the Aspire app host process.

[AlexRapida]

Full proccess tree is in attachment.

The actual nodejs proccess PID serving the app: 140928

tree.txt - when AppHost is running
tree2.txt - when it's stopped

[alechka]

oh, sorry, ^ was my other account %)

[karolz-ms]

Hmm. I tried on a Mac and it worked just fine for me... Will try on a Linux box next.

[karolz-ms]

I tried on openSUSE, not repro... 🤔