Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

fix(cli): update e2e test to use new composio generate ts command path

jkomyno915ef25820b5
diff --git a/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/README.md b/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/README.md
index a903694e1..6dddd700e 100644
--- a/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/README.md
+++ b/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/README.md
@@ -1,10 +1,10 @@
# TypeScript .mjs Import Resolution Test
-Verifies that `composio ts generate` produces TypeScript files that compile correctly with `moduleResolution: "nodenext"`.
+Verifies that `composio generate ts` produces TypeScript files that compile correctly with `moduleResolution: "nodenext"`.
## Background
-When `composio ts generate --output-dir ./types` runs without `--transpiled`:
+When `composio generate ts --output-dir ./types` runs without `--transpiled`:
- Only `.ts` files are generated
- These files contain `import ... from "./foo.mjs"` statements
@@ -18,7 +18,7 @@ This causes `TS2307: Cannot find module './foo.mjs'` errors.
| Test | Description |
| ---------------------- | -------------------------------------------------------------- |
-| composio ts generate | Runs CLI to generate TypeScript files for hackernews toolkit |
+| composio generate ts | Runs CLI to generate TypeScript files for hackernews toolkit |
| File existence | Verifies generated .ts files exist |
| TypeScript compilation | Runs `tsc --noEmit` to check import resolution |
@@ -33,7 +33,7 @@ fixtures/
The fixture script:
1. Cleans up any previous generated files
-2. Runs `composio ts generate --toolkits hackernews --output-dir ./generated`
+2. Runs `composio generate ts --toolkits hackernews --output-dir ./generated`
3. Verifies generated `.ts` files exist
4. Runs `npx tsc --noEmit` to check TypeScript compilation
5. Fails if TS2307 errors occur (indicating `.mjs` import bug)
diff --git a/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/e2e.test.ts b/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/e2e.test.ts
index 802c0a2b0..321258a56 100644
--- a/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/e2e.test.ts
+++ b/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/e2e.test.ts
@@ -35,8 +35,8 @@ e2e(import.meta.url, {
expect(result.exitCode).toBe(0);
});
- it('composio ts generate succeeds', () => {
- expect(result.stdout).toContain('Test 1 passed: composio ts generate succeeded');
+ it('composio generate ts succeeds', () => {
+ expect(result.stdout).toContain('Test 1 passed: composio generate ts succeeded');
});
it('generated files exist', () => {
diff --git a/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/fixtures/index.mjs b/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/fixtures/index.mjs
index fba71ea49..c05958e86 100644
--- a/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/fixtures/index.mjs
+++ b/ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/fixtures/index.mjs
@@ -4,7 +4,7 @@
* This test verifies that generated TypeScript files with .mjs imports
* can be compiled successfully with moduleResolution: "nodenext".
*
- * The issue: When `composio ts generate` uses importExtension: 'mjs',
+ * The issue: When `composio generate ts` uses importExtension: 'mjs',
* the generated .ts files contain `import ... from "./foo.mjs"` statements.
* With moduleResolution: "node16" or "nodenext", TypeScript expects .mjs
* imports to resolve to .mts files, NOT .ts files.
@@ -31,19 +31,19 @@ if (existsSync(GENERATED_DIR)) {
rmSync(GENERATED_DIR, { recursive: true });
}
-// Test 1: Run composio ts generate --toolkits hackernews --output-dir ./generated
-console.log('Test 1: Running composio ts generate --toolkits hackernews --output-dir ./generated...');
+// Test 1: Run composio generate ts --toolkits hackernews --output-dir ./generated
+console.log('Test 1: Running composio generate ts --toolkits hackernews --output-dir ./generated...');
try {
// Use the composio CLI binary built and installed to /usr/local/bin in the Dockerfile
- execSync(`composio ts generate --toolkits hackernews --output-dir ${GENERATED_DIR}`, {
+ execSync(`composio generate ts --toolkits hackernews --output-dir ${GENERATED_DIR}`, {
cwd: __dirname,
stdio: 'inherit',
env: { ...process.env, FORCE_COLOR: '0' },
});
- console.log('✅ Test 1 passed: composio ts generate succeeded\n');
+ console.log('✅ Test 1 passed: composio generate ts succeeded\n');
} catch (error) {
- console.error('❌ Test 1 failed: composio ts generate threw an error');
+ console.error('❌ Test 1 failed: composio generate ts threw an error');
console.error(error.message);
process.exit(1);
}