ts-jest doesn't see some of the app modules, however app itself working well

Created on 5 May 2020  ·  7Comments  ·  Source: kulshekhar/ts-jest

🐛 Bug Report

To Reproduce

Steps to reproduce the behavior:

Expected behavior

All modules are defined as in default app launch.

Link to repo (highly encouraged)

How can one create a repository without knowing the cause of the error?

Debug log:

 Utils › PostgreSQL › resultsToList

    TypeError: Cannot read property 'connect' of undefined

      30 |             await PostgreSQL.initialize();
      31 |         } catch (error) {
    > 32 |             throw new Error(error);
         |                   ^
      33 |         }
      34 | 
      35 | 

      at Function.run (src/api/app.ts:32:19)
      at Object.<anonymous> (src/api/main.ts:35:5)
      at Object.<anonymous> (src/services/couchDb.ts:4:1)
      at Object.<anonymous> (src/api/models/order.ts:7:1)
      at Object.<anonymous> (utils/dummy-data/order.ts:3:1)
      at Object.<anonymous> (tests/unit.test.ts:15:1)

File structure

/src/...
/tests/...
/tsconfig.json

Jest config

// package.json
...
"jest": {
    "verbose": true,
    "preset": "ts-jest",
    "cacheDirectory": "tests/temp"
  }
...

tsconfig.json

{
  "compilerOptions": {
    /* Basic Options */
    // "incremental": true,                   /* Enable incremental compilation */
    "target": "ES2017",
    /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019' or 'ESNEXT'. */
    "module": "CommonJS",
    /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */

    "sourceMap": true,
    /* Generates corresponding '.map' file. */
    // "outFile": "./",                       /* Concatenate and emit output to single file. */
    "outDir": "./dist",
    /* Redirect output structure to the directory. */
    "rootDir": "./",
    /* Specify the root directory of input files. Use to control the output directory structure with --outDir. */
    // "composite": true,                     /* Enable project compilation */
    // "tsBuildInfoFile": "./",               /* Specify file to store incremental compilation information */
    "removeComments": true,
    /* Do not emit comments to output. */
    "noEmit": true,
    /* Do not emit outputs. */
    // "importHelpers": true,                 /* Import emit helpers from 'tslib'. */
    // "downlevelIteration": true,            /* Provide full support for iterables in 'for-of', spread, and destructuring when targeting 'ES5' or 'ES3'. */
    // "isolatedModules": true,               /* Transpile each file as a separate module (similar to 'ts.transpileModule'). */
    /* Strict Type-Checking Options */
    "strict": false,
    /* Enable all strict type-checking options. */
    "noImplicitAny": false,
    /* Raise error on expressions and declarations with an implied 'any' type. */
    // "strictFunctionTypes": true,           /* Enable strict checking of function types. */
    // "strictBindCallApply": true,           /* Enable strict 'bind', 'call', and 'apply' methods on functions. */
    // "strictPropertyInitialization": true,  /* Enable strict checking of property initialization in classes. */
    "noImplicitThis": true,
    /* Raise error on 'this' expressions with an implied 'any' type. */
    "alwaysStrict": true,
    /* Parse in strict mode and emit "use strict" for each source file. */
    /* Additional Checks */
    //    "noUnusedLocals": true,                /* Report errors on unused locals. */
    //    "noUnusedParameters": true,            /* Report errors on unused parameters. */

    // "noImplicitReturns": true,             /* Report error when not all code paths in function return a value. */
    // "noFallthroughCasesInSwitch": true,    /* Report errors for fallthrough cases in switch statement. */
    /* Module Resolution Options */
    "moduleResolution": "node",
    /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
    "baseUrl": "./",
    /* Base directory to resolve non-absolute module names. */
    /* List of root folders whose combined content represents the structure of the project at runtime. */
    "typeRoots": [
      "./node_modules/@types"
    ],
    /* List of folders to include type definitions from. */
    // "types": [],                           /* Type declaration files to be included in compilation. */
    "allowSyntheticDefaultImports": true,
    /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */
    "esModuleInterop": true,
    /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
    // "preserveSymlinks": true,              /* Do not resolve the real path of symlinks. */
    // "allowUmdGlobalAccess": true,          /* Allow accessing UMD globals from modules. */
    /* Source Map Options */
    // "sourceRoot": "",                      /* Specify the location where debugger should locate TypeScript files instead of source locations. */
    // "mapRoot": "",                         /* Specify the location where debugger should locate map files instead of generated locations. */
    // "inlineSourceMap": true,               /* Emit a single file with source maps instead of having a separate file. */
    // "inlineSources": true,                 /* Emit the source alongside the sourcemaps within a single file; requires '--inlineSourceMap' or '--sourceMap' to be set. */
    /* Experimental Options */
    "experimentalDecorators": true,
    /* Enables experimental support for ES7 decorators. */
    "emitDecoratorMetadata": true,
    /* Enables experimental support for emitting type metadata for decorators. */
    "downlevelIteration": true,
    "watch": false
  },
  "include": [
    "./**/*"
  ],
  "exclude": [
    "./node_modules"
  ]
}

To Reproduce

I have no idea.

Question

All 7 comments

Please provide us a minimum repo for your issue :)

also please follow the bug report template, that would help us a lot to support you.

@ahnpnl I found and fixed the issue, thanks. The problem was in messed up ts-jest debug log, it shows non-existent problems instead of real ones.

@akopchinskiy Can you clarify what you mean?

The problem was in messed up ts-jest debug log, it shows non-existent problems instead of real ones

I'm also facing an issue where ts-jest is producing phantom type errors when tsc and VS Code are giving me a clean compile and no problems ...

@jedrichards you can try ts-jest@next to see if it fixes your issue.

@ahnpnl Ah! That fixed it!

@jedrichards 25.5.1 is out

Was this page helpful?
0 / 5 - 0 ratings

Related issues

RiJung picture RiJung  ·  4Comments

qm3ster picture qm3ster  ·  3Comments

golddranks picture golddranks  ·  3Comments

Slessi picture Slessi  ·  3Comments

bySabi picture bySabi  ·  4Comments