Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typescript support: support / load user defined tsconfig.json for transpiling files #7006

CSchulz opened this issue Apr 14, 2020 · 10 comments
topic: typescript v4.4.0 🐛 Issue present since 4.4.0


Copy link

CSchulz commented Apr 14, 2020

Current behavior:


import { forward } from '@apps/commons-e2e';

Fails with

Error: Cannot find module '@apps/commons-e2e' from 'e2e\src\integration'

Desired behavior:

ts-node should load an user defined tsconfig.json to find own path mappings.

Test code to reproduce

  1. create a tsconfig.json with a path mapping to a lib
  2. create a spec file using this path mapping
  3. run cypress



Copy link

I just tried to upgrade to 4.4.0 and ended up with the same error.

Everything was working just fine with that version but if I try to take advantage of the new feature:

TypeScript test files are now supported without using special preprocessors plugins. Addresses #1859.

To have it working previously I had to do the following:

const TsconfigPathsPlugin = require('tsconfig-paths-webpack-plugin');

module.exports = {
  resolve: {
    extensions: ['.ts', '.js'],
    plugins: [
      new TsconfigPathsPlugin({
        configFile: './tsconfig.json',
  module: {
    rules: [
        test: /\.ts$/,
        exclude: [/node_modules/],
        use: [
            loader: 'ts-loader',
            options: {
              configFile: 'tsconfig.e2e.json',

Copy link

kpittman-securus commented Apr 15, 2020

I am having trouble with 4.4.0 and TypeScript files also. When I run a build with my own tsconfig.json and then use the generated *.spec.js files for my specs, Cypress works fine.

When I run Cypress against all of my *.spec.ts files, 90% of them work fine, but 10% give cryptic error messages about Unexpected Tokens.

I say "cryptic" messages because A. the TS files compile just fine on their own, and B. the error message points to a line:column number that makes no sense (issue with not having sourcemaps maybe?)

Oops...we found an error preparing this test file:

The error was:
Error: Parsing file C:\path\to\my.helper.ts: Unexpected token (55:12)  

This occurred while Cypress was compiling and bundling your test code. This is usually caused by:
- A missing file or dependency
- A syntax error in the file or one of its dependencies
Fix the error in your code and re-run your tests.

When I look at my.helper.ts line 55 is something like this:

export function myFunction(s: string) {
//         ^ this is char 12 where Cypress says there is an error
//           clearly something is not correct about line:col in error message

At best, this would work flawlessly (maybe needs to parse my tsconfig.json?)
At minimum, it would be nice if the error log displayed the correct line number.
If we can't show the right line number for some reason, it would be nice if the log contained the actual line of source it is choking on.

@jennifer-shehane jennifer-shehane added the v4.4.0 🐛 Issue present since 4.4.0 label Apr 16, 2020
Copy link

Reproducible test case in

Copy link

@jennifer-shehane any update on the status for this one?

Copy link

I'm on Cypress 4.7.0 and running into something that looks remarkably similar to this. I'm seeing cryptic syntax errors on line:columns that make no sense (in my case, they are empty lines).

Copy link

Hoping this gets picked up soon. We are trying to move to typescript and eliminate relative path hell

Copy link

csnate commented Jun 10, 2020

I'm hitting the same error on my build server (running cypress/included:4.8.0 docker image) with a better error message:

The error was:

function attemptPasswordReset(email: string) {
ParseError: Unexpected token

This occurred while Cypress was compiling and bundling your test code.

This is only occurring in *.spec.ts files that have a custom function defined with typed parameters. I am also including my own tsconfig.json that sits at the same root directory as cypress.json and package.json.


  "compilerOptions": {
    "strict": true,
    "baseUrl": "../node_modules",
    "target": "es5",
    "lib": ["es5", "dom"],
    "types": ["cypress", "node"]
  "include": [

No errors occur when running locally with cypress open (running cypress@4.8.0)

Copy link

eric-burel commented Jun 23, 2020

Good, I am not alone. I can reproduce this issue only in my Docker image, using cypress/base:11, while tests work fine locally without even specifying the configFile of ts-loader.
Edit: with Cypress 4.8.0
Edit 2: aaaand I can repro only in my private application, though systematically. Maybe an update to 4.9 could solve it, will try again later.
And error message:

Error: Webpack Compilation Error
[tsl] ERROR
      TS18003: No inputs were found in config file 'tsconfig.json'. Specified 'include' paths were '["../node_modules/cypress","*/*.ts"]' and 'exclude' paths were '["../node_modules","../**/*.stories.tsx","../**/stories.tsx","../cypress"]'

The issue is the incorrect tsconfig.json being loaded, that's quite weird

@cypress-bot cypress-bot bot added stage: work in progress There is an open PR for this issue [WIP] stage: needs review The PR code is done & tested, needs review stage: pending release and removed stage: ready for work The issue is reproducible and in scope stage: work in progress There is an open PR for this issue [WIP] stage: needs review The PR code is done & tested, needs review labels Aug 7, 2020
Copy link

cypress-bot bot commented Aug 10, 2020

The code for this is done in cypress-io/cypress#7982, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@sync-by-unito sync-by-unito bot closed this as completed Aug 10, 2020
Copy link

cypress-bot bot commented Aug 20, 2020

Released in 5.0.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v5.0.0, please open a new issue.

@cypress-bot cypress-bot bot locked as resolved and limited conversation to collaborators Aug 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
topic: typescript v4.4.0 🐛 Issue present since 4.4.0
None yet

No branches or pull requests

10 participants