Case-sensetive folder name breaks on Linux

[alexander-daniel]

Hey again!

I'm running into a really odd issue.

v1.3.5

I can see that the lib/components/sketch here has 'sketch' as lower-case:
https://github.com/casesandberg/react-color/tree/master/lib/components

And the import of that component is made with lower-case:
https://github.com/casesandberg/react-color/blob/master/lib/components/SketchPicker.js#L35

However! When npm installing (npm i [email protected]), I noticed that the folder has an uppercase first letter. This won't cause any problems on OSX, however Linux is case-sensitive, so we get the following when trying to build/bundle on our CI servers (running Ubuntu):

Error: Cannot find module './sketch/Sketch' from '/myproject/node_modules/react-color/lib/components'

It seems to be searching for the lower-case, but I SSH'd into the test-box and saw this:

So perhaps you're publishing from your local repo and the directory name has an uppercase? Not too sure how there could be sync issues between the github repo and the npm package, as cloning this repo works just fine and the folders are all appropriately-cased.

It is only when you npm i react-color that this issue occurs.

Any ideas? Thanks for your time!

[mdoelker]

I can confirm this behaviour starting version 1.3.5.

[benjie]

Try:

git config core.ignorecase false

it may help detect these types of issues earlier. I've found it's slightly weird, but definitely better than nothing!

[liesislukas]

i have same issue. Moved project from os x to ubuntu and it broke. Removed react-color dependency.

[asaldivar]

+1

[tamagokun]

Have been running into this as well!

[vramana]

Can this be problem with npm ??

[nashaddams]

same problem here when deploying on debian. i think it's a problem with npm too. when cloning the repo from github everythink looks fine. when installing via npm the sketch folder is still uppercase.

[casesandberg]

Ah, this bug drove me insane a few months ago. I have completely renamed the folder so we shouldnt run into any more issues!

Update to [email protected]

[ghostCoder]

Can anyone confirm if [email protected] fixed this issue?
I am still getting it with [email protected]...

[alexander-daniel]

@ghostCoder Can confirm it's working for me with 1.3.6