v0.9.0

Author: danielcampagnolitg

.github/workflows/playwright.yml

@@ -0,0 +1,27 @@
+name: Playwright Tests
+on:
+  push:
+    branches: [ main, master ]
+  pull_request:
+    branches: [ main, master ]
+jobs:
+  test:
+    timeout-minutes: 60
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - uses: actions/setup-node@v4
+      with:
+        node-version: lts/*
+    - name: Install dependencies
+      run: npm ci
+    - name: Install Playwright Browsers
+      run: npx playwright install --with-deps
+    - name: Run Playwright tests
+      run: npx playwright test
+    - uses: actions/upload-artifact@v4
+      if: ${{ !cancelled() }}
+      with:
+        name: playwright-report
+        path: playwright-report/
+        retention-days: 30

.node-version

@@ -0,0 +1 @@
+v22.14.0

.nvmrc

@@ -1 +1 @@
-22.10.0
+22.14.0

.typedai.json

@@ -0,0 +1,19 @@
+[
+  {
+    "baseDir": "./",
+    "language": "typescript",
+    "initialise": "node build.js install",
+    "compile": "node build.js build",
+    "format": "",
+    "staticAnalysis": "node build.js lint",
+    "test": "npm run test",
+    "languageTools": "typescript",
+    "devBranch": "main",
+    "indexDocs": [
+      "src/**/*.ts",
+      "frontend/src/**/*.ts",
+      "bin/**",
+      "shared/**"
+    ]
+  }
+]

DOCS.md

@@ -256,4 +256,45 @@ const checkPromises = filesToStat.map(async (filename) => {
 Use single line statements where reasonable. This is a good candidate is there is not much complexity, only the single if statement.
 The empty catch block can definitely be on a single line with the comment
 
+# Example
+## Original code
+```typescript
+
+// Parse the config content
+let config: any;
+try {
+    config = yaml.load(configContent);
+} catch (error: any) {
+    logger.warn(`Failed to parse YAML ${configPath}: ${error.message}`);
+    return; // Stop if parsing fails
+}
 
+```
+## Updated code
+```typescript
+
+let config: any;
+try {
+    config = yaml.load(configContent);
+} catch (error: any) {
+    logger.warn(`Failed to parse YAML ${configPath}: ${error.message}`);
+    return;
+}
+
+```
+## Notes
+This code block does a simple load, there's no business logic.
+The between the `yaml.load` and the warn message is enough for the reader to quickly understand. No further comments are required.
+
+# Example
+
+## Orignal
+```
+const maxAttempts = 3; // Max reflection attempts
+```
+## Updated
+```typescript
+const maxReflectionAttempts = 3;
+```
+## Notes
+Use descriptive variable and function names instead of commenting on generic names.

Dockerfile.dev

@@ -3,48 +3,108 @@ FROM python:3.11-slim
 
 ENV DEBIAN_FRONTEND=noninteractive
 
-# Update package lists without signature verification to avoid "At least one invalid signature was encountered." on debian repos
+# Update package lists
 RUN apt-get -o Acquire::Check-Valid-Until=false -o Acquire::AllowInsecureRepositories=true -o Acquire::AllowDowngradeToInsecureRepositories=true update
 
+# Install base dependencies + Python build dependencies for pyenv
 # make g++ gcc build-essential are needed for node-gyp
-RUN apt-get install -y curl make g++ gcc build-essential git
-RUN curl -sL https://deb.nodesource.com/setup_20.x -o nodesource_setup.sh
-RUN bash ./nodesource_setup.sh
-RUN apt-get install -y nodejs
+# Others are common for building Python versions with pyenv
+RUN apt-get install -y --no-install-recommends \
+    curl make g++ gcc build-essential git \
+    libssl-dev zlib1g-dev libbz2-dev \
+    libreadline-dev libsqlite3-dev wget llvm \
+    libncursesw5-dev xz-utils tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev \
+    && rm -rf /var/lib/apt/lists/*
 
-RUN pip install aider-chat google-cloud-aiplatform "anthropic[vertex]"
+# Install Node.js
+RUN curl -sL https://deb.nodesource.com/setup_20.x -o nodesource_setup.sh \
+    && bash ./nodesource_setup.sh \
+    && apt-get install -y nodejs \
+    && rm nodesource_setup.sh
 
-ENV user=typedai
-ENV homedir=/home/typedai/
-RUN useradd --create-home -g users typedai
+# Install global Python packages
+RUN pip install aider-chat google-cloud-aiplatform "anthropic[vertex]" youtube-transcript-api
 
-WORKDIR $homedir
+# Define user and home directory consistently
+ENV USER_NAME=typedai
+ENV HOMEDIR=/home/${USER_NAME}
 
+# Create user with a specific home directory
+# Consider adding -u <UID> if you need a fixed UID, e.g., -u 1000
+RUN useradd --create-home -d ${HOMEDIR} -g users ${USER_NAME}
+
+# Set working directory (HOMEDIR is now defined)
+WORKDIR ${HOMEDIR}
+
+# Copy application files that are needed before USER switch or owned by root initially (if any)
+# For .husky and package.json, it's usually better to copy them after USER switch
+# so the user owns them, or chown them.
+
+# Copy .python-version file from build context (TYPEDAI_HOME) to the user's home directory in the image
+# This must exist in your TYPEDAI_HOME directory.
+COPY .python-version ${HOMEDIR}/.python-version
+# Ensure the user will own it (important if copied before USER switch, good practice anyway)
+RUN chown ${USER_NAME}:users ${HOMEDIR}/.python-version
+
+# Copy .husky files (assuming they are at the root of TYPEDAI_HOME)
 RUN mkdir ".husky"
 COPY .husky/install.mjs .husky/install.mjs
+RUN chown -R ${USER_NAME}:users ${HOMEDIR}/.husky
 
+# Copy main package.json and install dependencies
 COPY package*.json ./
+# Make chown of lock file optional
+RUN chown ${USER_NAME}:users package.json package-lock.json 2>/dev/null || chown ${USER_NAME}:users package.json
+
+# Switch to non-root user
+USER ${USER_NAME}
+
+# Now, as the user, install npm dependencies
 RUN npm install
 
 # Install Angular dependencies and build Angular app
-WORKDIR $homedir/frontend
-COPY frontend/package*.json ./
+# Ensure frontend/package.json exists in your TYPEDAI_HOME/frontend
+WORKDIR ${HOMEDIR}/frontend
+COPY --chown=${USER_NAME}:users frontend/package.json ./
+# COPY frontend/yarn.lock ./ # if you use yarn
+# If frontend/package-lock.json exists in your TYPEDAI_HOME/frontend, copy it with correct ownership.
+# If it doesn't exist, this COPY command will fail. If it's optional, remove this line.
+COPY --chown=${USER_NAME}:users frontend/package-lock.json ./
+
 RUN npm install
+# RUN npm run build # If you need to build frontend during Docker image creation
 
 # Set work directory back to home
-WORKDIR $homedir
+WORKDIR ${HOMEDIR}
 
-# Switch to non-root user
-USER $user
+# Install pyenv for the typedai user
+RUN git clone https://github.com/pyenv/pyenv.git ${HOMEDIR}/.pyenv
+
+# Add pyenv bin directory to the PATH for the typedai user
+ENV PYENV_ROOT="${HOMEDIR}/.pyenv"
+# Add shims dir too, and move comment
+ENV PATH="${PYENV_ROOT}/bin:${PYENV_ROOT}/shims:${PATH}"
+
+# This comment was on the ENV PATH line before, moving it here:
+# This sets PATH for subsequent RUN commands in Dockerfile and for the runtime environment
+
+# Initialize pyenv, install Python version from .python-version, and set it globally for pyenv
+# Ensure .python-version was copied earlier and is readable
+RUN eval "$(pyenv init --path)" && \
+    eval "$(pyenv init -)" && \
+    eval "$(pyenv virtualenv-init -)" && \
+    pyenv install --skip-existing $(cat ${HOMEDIR}/.python-version) && \
+    pyenv global $(cat ${HOMEDIR}/.python-version) && \
+    pyenv rehash
 
 ENV NODE_ENV=production
 
-# Needed to avoid the error "fatal: detected dubious ownership in repository at '/home/typedai'" when running git commands
-# as the application files are owned by the root user so an agent (which runs as the typedai user) can't modify them.
-RUN git config --global --add safe.directory /home/typedai
+# Needed to avoid "fatal: detected dubious ownership in repository"
+# This applies to /home/typedai because it's mounted from the host and owned by host's user in many cases
+RUN git config --global --add safe.directory ${HOMEDIR}
+# If your /workspace is also a git repo and you run git commands there:
+# RUN git config --global --add safe.directory /workspace
 
-# In the frontend package.json the `ng serve` needs the arg --host 0.0.0.0 for it to be available from the host machine
 EXPOSE 4200
 EXPOSE 3000
 CMD ["./bin/cmd-script"]
-

README.md

@@ -36,6 +36,21 @@ Included are capable software engineering agents, which have assisted building t
 - OpenTelemetry based observability
 - Leverages the extensive Python AI ecosystem through executing Python scripts/packages
 
+## CLI Usage
+
+TypedAI provides powerful command-line tools for automation and development workflows:
+
+```bash
+# Quick examples using the ai wrapper script
+ai query "What test frameworks does this repository use?"
+ai code "Add error handling to the user authentication function"  
+ai research "Latest developments in large language models"
+```
+
+The `ai` script runs locally while `aid` runs in Docker for isolation. Both provide access to all CLI agents including the specialized `codeAgent` for autonomous code editing tasks.
+
+For comprehensive CLI documentation, see the [CLI Usage Guide](https://typedai.dev/cli-usage/).
+
 ## Autonomous agents
 
 - Reasoning/planning inspired from Google's [Self-Discover](https://arxiv.org/abs/2402.03620) and other papers

bin/ai-sdk-versions.ts

@@ -0,0 +1,129 @@
+import * as fs from 'fs/promises'; // Use promises version for async/await
+import * as path from 'path';
+
+// Official provider packages are at https://github.com/vercel/ai/tree/main/packages
+
+// Define a basic type for the structure of package.json we care about
+interface PackageJson {
+    dependencies?: {
+        [key: string]: string;
+    };
+    // We don't need devDependencies, peerDependencies etc. for this task,
+    // but you could add them here if needed.
+}
+
+/**
+ * Analyzes package.json files under node_modules/@ai-sdk/
+ * to find the versions of @ai-sdk/provider and @ai-sdk/provider-utils
+ * in their dependencies.
+ */
+async function analyzeAiSdkDependencies(): Promise<void> {
+    const nodeModulesPath = path.join(process.cwd(), 'node_modules');
+    const aiSdkDir = path.join(nodeModulesPath, '@ai-sdk');
+
+    console.log(`--- Analyzing dependencies under ${aiSdkDir} ---`);
+    console.log(`(Ensure you are running this from your project's root directory)`);
+    console.log('--------------------------------------------------\n');
+
+
+    try {
+        // Check if the base node_modules/@ai-sdk directory exists
+        try {
+            await fs.access(aiSdkDir);
+        } catch (error: any) {
+            if (error.code === 'ENOENT') {
+                console.error(`Error: Directory not found: ${aiSdkDir}`);
+                console.error("Please ensure you are running this script from your project's root directory and have installed your @ai-sdk packages.");
+            } else {
+                console.error(`An unexpected error occurred checking directory ${aiSdkDir}: ${error.message}`);
+            }
+            return; // Exit the function if the directory isn't found or accessible
+        }
+
+        // Read the list of entries (files/directories) within @ai-sdk
+        const entries = await fs.readdir(aiSdkDir);
+
+        let providerVersion;
+        let providerUtilVersion;
+
+        // Process each entry found in the @ai-sdk directory
+        for (const entryName of entries) {
+            if(entryName === 'ui-utils' || entryName === 'react') continue;
+            const packageJsonPath = path.join(aiSdkDir, entryName, 'package.json');
+
+            if (entryName === 'provider' || entryName === 'provider-utils') {
+                const fileContent = await fs.readFile(packageJsonPath, 'utf8');
+                const packageJson: any = JSON.parse(fileContent);
+                if(entryName === 'provider-utils') {
+                    providerUtilVersion = packageJson.version
+                }
+                if(entryName === 'provider') {
+                    providerVersion = packageJson.version
+                }
+                continue;
+            }
+
+            console.log(`--- ${entryName} ---`);
+
+            try {
+                // Check if the entry is likely a directory by trying to access its package.json
+                // This implicitly handles non-directories or directories without package.json
+                await fs.access(packageJsonPath, fs.constants.R_OK); // Check if file exists and is readable
+
+                // Read and parse the package.json file
+                const fileContent = await fs.readFile(packageJsonPath, 'utf8');
+                const packageJson: PackageJson = JSON.parse(fileContent);
+
+                const dependencies = packageJson.dependencies;
+
+                // Check if the dependencies block exists and is an object
+                if (dependencies && typeof dependencies === 'object') {
+                    const providerVersion = dependencies['@ai-sdk/provider'];
+                    const providerUtilsVersion = dependencies['@ai-sdk/provider-utils'];
+
+                    if (providerVersion !== undefined) {
+                        console.log(`  @ai-sdk/provider: ${providerVersion}`);
+                    } else {
+                        console.log(`  @ai-sdk/provider: Not found in dependencies`);
+                    }
+
+                    if (providerUtilsVersion !== undefined) {
+                        console.log(`  @ai-sdk/provider-utils: ${providerUtilsVersion}`);
+                    } else {
+                        console.log(`  @ai-sdk/provider-utils: Not found in dependencies`);
+                    }
+                } else {
+                    console.log('  No "dependencies" block found in package.json');
+                }
+
+            } catch (error: any) {
+                // Handle errors specific to processing one package.json file
+                if (error.code === 'ENOENT') {
+                    // File not found (most likely because entryName wasn't a directory with a package.json)
+                    console.warn(`  Warning: No package.json found or accessible at ${packageJsonPath}`);
+                } else if (error instanceof SyntaxError) {
+                    // JSON parsing error
+                    console.warn(`  Warning: Invalid JSON in ${packageJsonPath}: ${error.message}`);
+                } else {
+                    // Other potential errors like permissions issues
+                    console.error(`  Error processing package.json for ${entryName}: ${error.message}`);
+                }
+            }
+            console.log(''); // Add a blank line for separation between packages
+        }
+
+        console.log();
+        console.log('Provider version: ', providerVersion);
+        console.log('Provider util version: ', providerUtilVersion);
+        console.log();
+
+        console.log('--- Analysis Complete ---');
+
+    } catch (error: any) {
+        // Handle errors during the initial directory read or other unexpected issues
+        console.error(`An unexpected error occurred during analysis: ${error.message}`);
+    }
+}
+
+// Execute the function
+analyzeAiSdkDependencies().catch(console.error);