Noderedagent - launch.json not created for testing and publishing to OpenCore

OpenCore
1

Hi @Allan_Zimmermann

I have a brand new OpenCore instance that I deployed. I am now trying to publish a noderedagent to the OpenCore instance that I can run on remote nodeagents as a package.

I follow the instructions ( GitHub - openiap/noderedagent · GitHub ) to run it as a package and publish to my OpenCore instance. When I run the initialise step, the package.json is generated but there is no launch.json file generated (the .env file is generated though).

Therefore, I can’t test the noderedagent in VS Code (as with a previous OpenCore instance I had). I then took a chance to pack and deploy to OpenCore, but the package is not available to select in my OpenCore instance to run as a package on a remote agent.

Am I missing something or why is the launch.json file not generated when initialising the cloned repo with the openiap-assistant?

OpenCore v1.5.12.62
Visual studio code v1.115.0

2

The extension no longer creates a launch file. Those are already in the example repos. There are so many different ways people might want to run their code, so I decided to “back down” and only maintain the .env file.

3

Thanks Allan.

Added my own launch.json from examples and got it running.