staklink 0.3.43 → 0.3.44

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -56941,7 +56941,7 @@ var SSEManager = class {
56941
56941
  var sseManager = new SSEManager();
56942
56942
 
56943
56943
  // src/proxy/version.ts
56944
- var VERSION = "0.3.43";
56944
+ var VERSION = "0.3.44";
56945
56945
 
56946
56946
  // node_modules/uuid/dist/esm/stringify.js
56947
56947
  var byteToHex = [];
@@ -111161,23 +111161,27 @@ __export(repair_exports, {
111161
111161
  });
111162
111162
  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.
111163
111163
 
111164
- 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:
111164
+ 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 (put the exact raw content of the files in the XML tags, no extra text like triple backticks or language label). FOR YOUR FINAL TEXT RESPONSE, USE THE THE FOLLOWING XML FORMAT:
111165
111165
 
111166
111166
  <status>COMPLETE</status>
111167
111167
  <pm2.config.js>
111168
- ...pm2 config file contents here...
111168
+ module.exports = {
111169
+ apps: [ ... ]
111170
+ };
111169
111171
  </pm2.config.js>
111170
111172
  <docker-compose.yaml>
111171
- ...docker-compose file contents here...
111173
+ version: "3.8"
111174
+ services:
111175
+ ...
111172
111176
  </docker-compose.yaml>
111173
111177
  <Dockerfile>
111174
- ...Dockerfile contents here...
111178
+ FROM ghcr.io/stakwork/staklink-js:latest
111175
111179
  </Dockerfile>
111176
111180
 
111177
111181
  IMPORTANT: YOU DO NOT NEED TO INCLUDE FILES THAT DID NOT CHANGE. Only include files that you modified.`;
111178
111182
  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.
111179
111183
 
111180
- 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.
111184
+ 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. REMEMBER: this is a development environment, so the pm2 script should be something like "npm run dev" or something similar... we want to default to whatever start script is best for development (like whatever has hot-reload etc).
111181
111185
 
111182
111186
  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.
111183
111187
 
@@ -10948,7 +10948,7 @@ var glob = Object.assign(glob_, {
10948
10948
  glob.glob = glob;
10949
10949
 
10950
10950
  // src/proxy/version.ts
10951
- var VERSION = "0.3.43";
10951
+ var VERSION = "0.3.44";
10952
10952
 
10953
10953
  // src/cli.ts
10954
10954
  var STAKLINK_PROXY = "staklink-proxy";
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "staklink",
3
3
  "displayName": "staklink",
4
4
  "description": "staklink process manager",
5
- "version": "0.3.43",
5
+ "version": "0.3.44",
6
6
  "type": "module",
7
7
  "publisher": "stakwork",
8
8
  "engines": {