Skip to content

Increase verbosity for "Module not found" errors, to prevent case sensitiveness problems #1278

Closed
@caesarsol

Description

@caesarsol

As discussed with @gaearon in #1260

My problem had to do with:

  • a local MacOS build (case insensitive) with files with the right casing
  • a git repository with wrong filenames casing
  • a remote CI build on a linux server, hence case sensitive

The CI builds failed, the local was OK, and I lost hours because I had no access to CI machine and I was misleaded by the undescriptive error message.

My proposal is to leverage something similar to the CaseSensitiveWebpackPlugin to give a more verbose error message, for example a directory listing or the searched paths.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions