Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 22, 03:15 UTC
fix(cli): update e2e test to use new composio generate ts command path
The E2E test for TypeScript .mjs import resolution was still using the old `composio ts generate` command which no longer exists as a top-level command after the generate restructure.
jkomyno committed
Mar 17, 2026 at 15:57 UTC
915ef25820b57d250ad7a7ec826f4a528109c7dc
3 files changed
+12
-12
ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/README.md
+4
-4
@@ -1,10 +1,10 @@
1
# TypeScript .mjs Import Resolution Test
2
3
-Verifies that `composio ts generate` produces TypeScript files that compile correctly with `moduleResolution: "nodenext"`.
3
+Verifies that `composio generate ts` produces TypeScript files that compile correctly with `moduleResolution: "nodenext"`.
4
5
## Background
6
7
-When `composio ts generate --output-dir ./types` runs without `--transpiled`:
7
+When `composio generate ts --output-dir ./types` runs without `--transpiled`:
8
9
- Only `.ts` files are generated
10
- These files contain `import ... from "./foo.mjs"` statements
@@ -18,7 +18,7 @@ This causes `TS2307: Cannot find module './foo.mjs'` errors.
18
19
| Test | Description |
20
| ---------------------- | -------------------------------------------------------------- |
21
-| composio ts generate | Runs CLI to generate TypeScript files for hackernews toolkit |
21
+| composio generate ts | Runs CLI to generate TypeScript files for hackernews toolkit |
22
| File existence | Verifies generated .ts files exist |
23
| TypeScript compilation | Runs `tsc --noEmit` to check import resolution |
24
@@ -33,7 +33,7 @@ fixtures/
33
The fixture script:
34
35
1. Cleans up any previous generated files
36
-2. Runs `composio ts generate --toolkits hackernews --output-dir ./generated`
36
+2. Runs `composio generate ts --toolkits hackernews --output-dir ./generated`
37
3. Verifies generated `.ts` files exist
38
4. Runs `npx tsc --noEmit` to check TypeScript compilation
39
5. Fails if TS2307 errors occur (indicating `.mjs` import bug)
ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/e2e.test.ts
+2
-2
@@ -35,8 +35,8 @@ e2e(import.meta.url, {
35
expect(result.exitCode).toBe(0);
36
});
37
38
- it('composio ts generate succeeds', () => {
39
- expect(result.stdout).toContain('Test 1 passed: composio ts generate succeeded');
38
+ it('composio generate ts succeeds', () => {
39
+ expect(result.stdout).toContain('Test 1 passed: composio generate ts succeeded');
40
});
41
42
it('generated files exist', () => {
ts/e2e-tests/runtimes/node/typescript-mjs-import-nodenext/fixtures/index.mjs
+6
-6
@@ -4,7 +4,7 @@
4
* This test verifies that generated TypeScript files with .mjs imports
5
* can be compiled successfully with moduleResolution: "nodenext".
6
*
7
- * The issue: When `composio ts generate` uses importExtension: 'mjs',
7
+ * The issue: When `composio generate ts` uses importExtension: 'mjs',
8
* the generated .ts files contain `import ... from "./foo.mjs"` statements.
9
* With moduleResolution: "node16" or "nodenext", TypeScript expects .mjs
10
* imports to resolve to .mts files, NOT .ts files.
@@ -31,19 +31,19 @@ if (existsSync(GENERATED_DIR)) {
31
rmSync(GENERATED_DIR, { recursive: true });
32
}
33
34
-// Test 1: Run composio ts generate --toolkits hackernews --output-dir ./generated
35
-console.log('Test 1: Running composio ts generate --toolkits hackernews --output-dir ./generated...');
34
+// Test 1: Run composio generate ts --toolkits hackernews --output-dir ./generated
35
+console.log('Test 1: Running composio generate ts --toolkits hackernews --output-dir ./generated...');
36
try {
37
// Use the composio CLI binary built and installed to /usr/local/bin in the Dockerfile
38
- execSync(`composio ts generate --toolkits hackernews --output-dir ${GENERATED_DIR}`, {
38
+ execSync(`composio generate ts --toolkits hackernews --output-dir ${GENERATED_DIR}`, {
39
cwd: __dirname,
40
stdio: 'inherit',
41
env: { ...process.env, FORCE_COLOR: '0' },
42
});
43
44
- console.log('✅ Test 1 passed: composio ts generate succeeded\n');
44
+ console.log('✅ Test 1 passed: composio generate ts succeeded\n');
45
} catch (error) {
46
- console.error('❌ Test 1 failed: composio ts generate threw an error');
46
+ console.error('❌ Test 1 failed: composio generate ts threw an error');
47
console.error(error.message);
48
process.exit(1);
49
}