question-mark
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.

[CaseSensitivePathsPlugin] Error, parsing some folders

See original GitHub issue

When importing folders like FooBar/index.js like:

import FooBar from ./FooBar

generates an error.

Module not found: Error: [CaseSensitivePathsPlugin] fullpath/Foobar.js does not match the corresponding path on disk - File does not exist.

But import like this works:

import Foobar from ./FooBar/index.js.

Or if I changed the folder name to Foobar, then also work.

Here’s the console script reference when I click on error:

errors: function(errors) {
        console.log("[WDS] Errors while compiling.");
        for(var i = 0; i < errors.length; i++)
                    // The below line in red underlined.
            console.error(stripAnsi(errors[i]));
        if(initial) return initial = false;
        reloadApp();
    },

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:8

github_iconTop GitHub Comments

9reactions
mchandlerazcommented, Mar 17, 2017

I got passed this error by just killing my webpack dev-server and restarting it. No need for renaming directories or anything.

1reaction
shenders13commented, Feb 16, 2017

I ran into this problem. When I looked at file structure in Folder (on Mac), the folder names weren’t exactly the same as they were on my Sublime Text editor (some folder names on Sublime were capitalized but not in my Finder). I changed the import path to fit the folder structure on Finder and it worked.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Module not found: [CaseSensitivePathsPlugin] `...\react.js ...
I'm new to react - but from what I can tell it's a pathing issue where npm install adds modules into the node_modules...
Read more >
Error: Path Does Not Match The Corresponding Path On Disk
js Module not found: [CaseSensitivePathsPlugin] some find file: 'index.js' does not match the corresponding name on disk: '. casesensitivepathswebpackplugin.
Read more >
webpack/webpack - module - Gitter
The problem is that my files are reading sass-loader without having been transpiled by rails-erb-loader . (Files that end in ...
Read more >
How to fix 'Module not found: Can't resolve 'http' in ... - YouTube
Basically, just change 'react-scripts' to 4.0.2 in your package.json and run `npm install` again :D Follow me on Twitter: ...
Read more >
Top 5 pnp-webpack-plugin Code Examples - Snyk
To help you get started, we've selected a few pnp-webpack-plugin examples, ... To fix this, we prevent you from importing files out of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found