Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Webpack Compilation Error when module is not imported

See original GitHub issue

Current behavior

Cypress throws Webpack Compilation Error when running following test file

const { fakeServer } = require("cypress/types/sinon")

describe('example to-do app', () => {
  it.only('displays two todo items by default', () => {
    fs.readFile("fileDoesn'tExist.js");
  });
});

Error: Webpack Compilation Error
./cypress/integration/1-getting-started/todo.spec.js
Module not found: Error: Can't resolve 'cypress/types/sinon' in '/home/amit/temp/cytorus_code/test-repository/test/cypress/integration/1-getting-started'
resolve 'cypress/types/sinon' in '/home/amit/temp/cytorus_code/test-repository/test/cypress/integration/1-getting-started'
  Parsed request is a module
  using description file: /home/amit/temp/cytorus_code/test-repository/package.json (relative path: ./test/cypress/integration/1-getting-started)
    Field 'browser' doesn't contain a valid alias configuration
    Looked for and couldn't find the file at the following paths:

Desired behavior

I’m expecting it to report the error in particular test with line number, if possible.

Test code to reproduce

You can reproduce this error with following code anywhere in the test

const { fakeServer } = require("cypress/types/sinon")

describe('example to-do app', () => {
  it('throws Webpack Compilation Error', () => {
    fs.readFile("fileDoesn'tExist.js"); //sorry-cypress not working
  });
});

const { fakeServer } = require("cypress/types/sinon")

describe('example to-do app', () => {
  it('throws Webpack Compilation Error', () => {
     cy.then( () => {
       throw new Error("on my wish");
     })
  });
});