staklink 0.3.41 → 0.3.43

package/dist/proxy-server.cjs

@@ -56941,7 +56941,7 @@ var SSEManager = class {
 var sseManager = new SSEManager();
 
 // src/proxy/version.ts
-var VERSION = "0.3.41";
+var VERSION = "0.3.43";
 
 // node_modules/uuid/dist/esm/stringify.js
 var byteToHex = [];
@@ -111159,7 +111159,7 @@ __export(repair_exports, {
   makePrompt: () => makePrompt,
   parseXML: () => parseXML
 });
-var SYSTEM = `You are a software systems expert. Your job is to help set up the development environment for a software project. Fix the user's pm2 config and/or docker-compose files, and use the pm2 and docker cli to get the project running. YOUR GOAL IS TO THE GET THE FIRST APP IN THE PM2 CONFIG FILE TO RUN CORRECTLY! Other apps and docker containers are only supporting services.
+var SYSTEM = `You are a software systems expert. Your job is to help set up the development environment for a software project. Fix the user's pm2 config and/or docker-compose files, and use the pm2 and docker cli to get the project running. YOUR GOAL IS TO THE GET THE frontend APP IN THE PM2 CONFIG FILE TO RUN CORRECTLY! Other apps and docker containers are only supporting services.
 
 When you have gotten the frontend running, or gotten as far as you can, respond to the user by saying either "<status>COMPLETE</status>" or "<status>FAILED</status>". If COMPLETE, then tell the user the fixed config files. FOR YOUR FINAL TEXT RESPONSE, USE THE THE FOLLOWING XML FORMAT:
 
@@ -111177,14 +111177,13 @@ When you have gotten the frontend running, or gotten as far as you can, respond
 IMPORTANT: YOU DO NOT NEED TO INCLUDE FILES THAT DID NOT CHANGE. Only include files that you modified.`;
 var makePrompt = (podConfigPath) => `Please inspect the current running environment, and try to fix it. The user tried to load the frontend on the defined PORT, but something went wrong.
 
-The config files can be read at ${podConfigPath}. You must find out how to edit the pm2.config.js and the docker-compose.yaml in order to get the project to run successfully (there is also a Dockerfile which may also be changed if absolutely needed).
+The config files can be read at ${podConfigPath}. You must find out how to edit the pm2.config.js and the docker-compose.yaml in order to get the project to run successfully (there is also a Dockerfile which may also be changed if absolutely needed). Focus on the frontend app defined in the pm2 config file, don't worry about other services unless they are needed to run the frontend. For example, if its a next.js app, you can read the package.json to see what SHOULD be in the pm2 "script" command or the special install/build/etc commands.
 
 This project is currently running a remote code-server instance. Docker is optional, but may be used. The docker-compose file has already been started. You can use the regular docker commands (docker ps, docker logs, etc) to inspect the running containers.
 
 The actual core project code is being run with pm2! You can use pm2 commands to inspect the running processes. However, there is another service running in pm2 also (called staklink-proxy), that is not part of the software project at hand. DO NOT run "pm2 logs" just like that... only read logs of specific processes from the pm2 config file one at a time! Your goal is to get all supporting services and processes running in order to run the main project frontend. (Of course, sometimes its just one simple frontend process without supporting services. It really just depends on the project).
 
 We have SPECIAL env vars for pm2, that tell the code-server system how to automatically build and start the project.
-- START_COMMAND: The command to start the project (e.g. npm start) [REQUIRED]
 - PORT: The port the project runs on (e.g. 3000)
 - INSTALL_COMMAND: The command to install dependencies (e.g. npm install)
 - BUILD_COMMAND: The command to build the project (e.g. npm run build)
@@ -111193,7 +111192,7 @@ We have SPECIAL env vars for pm2, that tell the code-server system how to automa
 - TEST_COMMAND: Command to run tests (e.g. npm test)
 - E2E_TEST_COMMAND: Command to run end-to-end tests (e.g. npx playwright test)
 
-When you have made a file change and want to restart the whole pm2 environment, do so like this: \`npx -y staklink reload\`. That will start the pm2 apps, then re-run all the install, build, pre-start, start commands if they are defined. The only required command is the START_COMMAND.
+When you have made a file change and want to restart the whole pm2 environment, do so like this: \`npx -y staklink reload\`. That will start the pm2 apps, then re-run all the install, build, pre-start commands if they are defined. None of these commands are required though, only the "script" is required (to start the frontend).
 
 Good luck!
 `;
@@ -113119,10 +113118,7 @@ ${diff.trim()}`);
           system: repair_exports.SYSTEM
         };
       },
-      (result) => ({
-        ...result,
-        repaired: true
-      })
+      (result) => repair_exports.parseXML(result)
     )
   );
   app.post("/repair", async (req, res) => {

package/dist/staklink-cli.cjs

@@ -10948,7 +10948,7 @@ var glob = Object.assign(glob_, {
 glob.glob = glob;
 
 // src/proxy/version.ts
-var VERSION = "0.3.41";
+var VERSION = "0.3.43";
 
 // src/cli.ts
 var STAKLINK_PROXY = "staklink-proxy";

package/package.json

@@ -2,7 +2,7 @@
   "name": "staklink",
   "displayName": "staklink",
   "description": "staklink process manager",
-  "version": "0.3.41",
+  "version": "0.3.43",
   "type": "module",
   "publisher": "stakwork",
   "engines": {