-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Closed
Labels
kind: bugSomething isn't workingSomething isn't working
Description
Verify canary release
- I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
https://github.com/bayesimpact/with-nest-turbo-tests-issue
Which canary version will you have in your reproduction?
turbo 2.5.9-canary.4
Environment information
turbo 2.5.9-canary.4
CLI:
Version: 2.5.9-canary.4
Path to executable: /Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/node_modules/turbo-darwin-arm64/bin/turbo
Daemon status: Running
Package manager: npm
Platform:
Architecture: aarch64
Operating system: macos
WSL: false
Available memory (MB): 29310
Available CPU cores: 12
Environment:
CI: None
Terminal (TERM): xterm-256color
Terminal program (TERM_PROGRAM): iTerm.app
Terminal program version (TERM_PROGRAM_VERSION): 3.6.2
Shell (SHELL): /bin/zsh
stdin: false
Expected behavior
npm test should work
Actual behavior
npm test fails
api:test:
api:test:
api:test: > api@0.0.0 test
api:test: > jest
api:test:
Error: Jest: Failed to parse the TypeScript config file /Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/apps/api/jest.config.ts
api:test: TSError: ⨯ Unable to compile TypeScript:
api:test: jest.config.ts:1:28 - error TS2307: Cannot find module '@repo/jest-config' or its corresponding type declarations.
api:test:
api:test: 1 import { nestConfig } from '@repo/jest-config';
api:test: ~~~~~~~~~~~~~~~~~~~
api:test:
api:test: at readConfigFileAndSetRootDir (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/node_modules/jest-config/build/readConfigFileAndSetRootDir.js:116:13)
api:test: at async readInitialOptions (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/node_modules/jest-config/build/index.js:403:13)
api:test: at async readConfig (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/node_modules/jest-config/build/index.js:147:48)
api:test: at async readConfigs (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/node_modules/jest-config/build/index.js:424:26)
api:test: at async runCLI (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/node_modules/@jest/core/build/cli/index.js:151:59)
api:test: at async Object.run (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/node_modules/jest-cli/build/run.js:130:37)
api:test: npm ERR! Lifecycle script `test` failed with error:
api:test: npm ERR! Error: command failed
api:test: npm ERR! in workspace: api@0.0.0
api:test: npm ERR! at location: /Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/apps/api
api:test:
api:test: ERROR: command finished with error: command (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/apps/api) /Users/jdoucy/.nvm/versions/node/v20.12.0/bin/npm run test exited (1)
api#test: command (/Users/jdoucy/Dev/bayesimpact/with-nest-turbo-tests-issue/apps/api) /Users/jdoucy/.nvm/versions/node/v20.12.0/bin/npm run test exited (1)
Tasks: 0 successful, 1 total
Cached: 0 cached, 1 total
Time: 1.179s
Failed: api#test
ERROR run failed: command exited (1)```
### To Reproduce
just launch `npm test`
### Additional context
_No response_
Neosoulink
Metadata
Metadata
Assignees
Labels
kind: bugSomething isn't workingSomething isn't working