staklink 0.3.40 → 0.3.41

package/dist/proxy-server.cjs

@@ -48679,7 +48679,6 @@ var PM2Manager = class {
     } catch (error85) {
       console.warn(`Failed to load env file: ${envFilePath}`, error85);
     }
-    console.log("envVars", envVars);
     return envVars;
   }
   async startProcess(processConfig) {
@@ -56942,7 +56941,7 @@ var SSEManager = class {
 var sseManager = new SSEManager();
 
 // src/proxy/version.ts
-var VERSION = "0.3.40";
+var VERSION = "0.3.41";
 
 // node_modules/uuid/dist/esm/stringify.js
 var byteToHex = [];
@@ -111176,7 +111175,7 @@ When you have gotten the frontend running, or gotten as far as you can, respond
 </Dockerfile>
 
 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.
+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).
 
@@ -111186,6 +111185,7 @@ The actual core project code is being run with pm2! You can use pm2 commands to
 
 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)
 - PRE_START_COMMAND: Commands to run before starting the project (e.g. npx prisma migrate dev)
@@ -111193,7 +111193,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: \`pm2 stop all && pm2 delete all && pm2 flush && npx -y staklink@latest start\`. That will restart the staklink-proxy server, which runs 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, start commands if they are defined. The only required command is the START_COMMAND.
 
 Good luck!
 `;

package/dist/staklink-cli.cjs

@@ -3738,7 +3738,6 @@ var PM2Manager = class {
     } catch (error) {
       console.warn(`Failed to load env file: ${envFilePath}`, error);
     }
-    console.log("envVars", envVars);
     return envVars;
   }
   async startProcess(processConfig) {
@@ -10949,7 +10948,7 @@ var glob = Object.assign(glob_, {
 glob.glob = glob;
 
 // src/proxy/version.ts
-var VERSION = "0.3.40";
+var VERSION = "0.3.41";
 
 // 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.40",
+  "version": "0.3.41",
   "type": "module",
   "publisher": "stakwork",
   "engines": {