-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
Netlify fails to resolve alias and build fails #2897
Comments
Not really sure — I'd keep following up on Linux/Mac differences. Perhaps if you have a Linux VM handy, start playing around with the site there. |
Ok, I had a quick look and it does fail on Linux (Ubuntu 12.04). I'm going to keep doing some tests.
*btw run into this problem #1905 |
Ok, when the directories were renamed in MacOS the repo kept the previous directory names since they are different (case-sensitive). Fixed in the Ubuntu box and pushed and is now working. I'm going to try to re-rename back to /src/sharedComponent/Foobar/index.js to see if it breaks, as Netlify doesn't seem to support Folder as Filename
|
Ah cool :-) Yeah I always use lowercase names as I've this issue way too many times haha :-D |
For future readers, the problem is related to So, renamed: src to src |
@heldrida But when I run the command locally it builds successfully but not working on netlify. |
@mddanishyusuf the issue above was related to directory and filenames. You need to test your build in a Linux VM, to see that the problems are related to case insensitivity in your original file system! |
I think that the best solution, in this case, is to change files name with |
For those still having this issue on macs, one other way to find the "true" capitalization of your filenames is to check the names on GitHub. You can then edit the filename directly on GH and pull the changes. Although nothing will change in your file system, your deploy to Netlify should work. |
The command
gatsby build
fails in the Netlify CI. This might be related to the plugingatsby-plugin-resolve-src
(which exists in the package.json devDependencies and dependencies):package.json:
The command
gatsby build
works fine in MacOS and alsogatsby serve
.It can be related to case sensitive imports, which I reviewed and doesn't seem to be the case, tias.
The components are named by the directory and not file, as in:
Assuming the following algorithm ( https://nodejs.org/api/modules.html#modules_all_together )
The .nvmrc is set to:
v8.4.0
The Netlify CI error log:
Renamed all the components to:
And fails importing CSS Modules:
The text was updated successfully, but these errors were encountered: