You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- temorary disable auto-release in release gh action
- describe currently not working buliding in docker
- improve building and running instructions in readme
- bump verison
- improve bulid script and dockerfile
4.The compiled executable will be created in the `dist` directory as `ai-console-agent`, along with source map files.
164
+
The compiled executable will be created in the `dist` directory as `ai-console-agent`.
166
165
167
166
#### Building in Docker
168
167
168
+
> **Note**: Building in Docker is currently not working and is a work in progress. The following steps are provided for reference but may not function as expected. We are actively working on resolving this issue.
169
+
169
170
1. Build the Docker image:
170
171
171
172
```
@@ -200,10 +201,14 @@ After successful compilation, run the AI Console Agent using:
200
201
./dist/ai-console-agent "Your command here"
201
202
```
202
203
204
+
Remember to use the double quotes around your command to avoid issues with special characters in you message.
205
+
203
206
This executable includes all necessary dependencies and can be distributed as a standalone program.
204
207
205
208
### Release Process for Developers
206
209
210
+
> **Note**: The automatic release process for this app via GitHub Actions is currently suspended due to critical errors in the build process of Bun. The executable produced by the GitHub Actions workflow contains a critical error that prevents the application from functioning correctly. As a result, only manual building is working at the moment. The release process described below is temporarily on hold until these issues are resolved.
211
+
207
212
To create a new release:
208
213
209
214
1. Ensure all changes are committed and pushed to the main branch.
@@ -237,7 +242,7 @@ Read about it here: https://bun.sh/docs/bundler/executables
237
242
238
243
If you encounter errors related to missing packages during compilation, follow these steps:
239
244
240
-
1. Identify the missing packages from the error messages. Common missing packages might include:
245
+
1. Identify the missing packages from the error messages. For example these were such problem packages (currently already included in dev deps, so theyre not a problem anymore):
241
246
242
247
- pg
243
248
-@xenova/transformers
@@ -255,7 +260,7 @@ If you encounter errors related to missing packages during compilation, follow t
255
260
bun add -d pg @xenova/transformers pgvector
256
261
```
257
262
258
-
3.Update your `package.json` to include these as dev dependencies:
263
+
3.Look that your `package.json` is updated to include these as dev dependencies:
259
264
260
265
```json
261
266
{
@@ -280,7 +285,10 @@ If you encounter errors related to missing packages during compilation, follow t
280
285
281
286
Note: This issue may occur if there are changes in the `llamaindex` package or its dependencies. Always check for updates and be prepared to add new dev dependencies as needed.
282
287
283
-
### Development Run
288
+
Currently adding such packages as dev deps resolves the issue with building project in a single executable.
289
+
The problem happens because of dynamic imports in deps of current project, so only adding them as dev deps helps.
290
+
291
+
### Development run
284
292
285
293
For development and testing purposes, you can run the project directly without compilation:
286
294
@@ -334,4 +342,4 @@ If you encounter any problems or have any questions, please open an issue on the
0 commit comments