Site coded in React works in localhost but strips CSS in Netlify prod

[edlr73]

Hello, my first time here! I have 2 sites on Netlify, and my personal page seems to have an issue. I don’t know if it’s possibly tied to CSS or what. The site is coded in React, and I checked to make sure all node modules are updated, but for some reason when I push my latest GitHub update, it works fine in my localhost, but all of the pictures and CSS setup seems to have not ported. The Netlify production deploy shows as published. My site is emitdelarosa.netlify.app.

Published build is:
9:17:06 AM: Build ready to start
9:17:08 AM: build-image version: 6dfe19d15f524c85d6f9bf7df9fb30b0a9f0a61a
9:17:08 AM: build-image tag: v3.3.10
9:17:08 AM: buildbot version: 0d19834c19ebfe54208907d729718495339fe085
9:17:08 AM: Fetching cached dependencies
9:17:08 AM: Starting to download cache of 254.9KB
9:17:08 AM: Finished downloading cache in 107.401454ms
9:17:08 AM: Starting to extract cache
9:17:08 AM: Failed to fetch cache, continuing with build
9:17:08 AM: Starting to prepare the repo for build
9:17:08 AM: No cached dependencies found. Cloning fresh repo
9:17:08 AM: git clone GitHub - emitdlr/edlrresume: My portfolio page - all in React (for the most part)
9:17:09 AM: Preparing Git Reference refs/heads/master
9:17:10 AM: Starting build script
9:17:10 AM: Installing dependencies
9:17:12 AM: v10.20.1 is already installed.
9:17:12 AM: Now using node v10.20.1 (npm v6.14.4)
9:17:13 AM: Attempting ruby version 2.6.2, read from environment
9:17:14 AM: Using ruby version 2.6.2
9:17:15 AM: Using PHP version 5.6
9:17:15 AM: 5.2 is already installed.
9:17:15 AM: Using Swift version 5.2
9:17:15 AM: Started restoring cached node modules
9:17:15 AM: Finished restoring cached node modules
9:17:15 AM: Started restoring cached yarn cache
9:17:15 AM: Finished restoring cached yarn cache
9:17:15 AM: Installing yarn at version 1.13.0
9:17:15 AM: Installing Yarn!
9:17:15 AM: > Downloading tarball…
9:17:15 AM: [1/2]: https://yarnpkg.c
9:17:15 AM: om/downloads/1.13.0/yarn-v1.13.0.tar.gz → /tmp/yarn.tar.gz.mZbIin738u
9:17:15 AM: % Total % Rec
9:17:15 AM: eived % Xferd Average Speed Time Time Time Current
9:17:15 AM: Dload Upload
9:17:15 AM: Total Spent Left
9:17:15 AM: Speed
9:17:15 AM:
0 0
9:17:15 AM: 0 0 0 0 0 0 --:–
9:17:15 AM: :-- --:–:-- --:–:-- 0
9:17:15 AM: 1
9:17:15 AM: 0
9:17:15 AM: 0
9:17:15 AM: 80 100 80
9:17:15 AM: 0
9:17:15 AM: 0
9:17:15 AM: 23
9:17:15 AM: 1
9:17:15 AM: 0
9:17:15 AM: -
9:17:15 AM: -:–
9:17:15 AM: :–
9:17:15 AM: --:
9:17:15 AM: --:–
9:17:15 AM: -
9:17:15 AM: -:–
9:17:15 AM: :–
9:17:15 AM: 23
9:17:15 AM: 1
9:17:15 AM: 0
9:17:15 AM: 0
9:17:15 AM: 0 0 0 0 0 0 --:–:-- --:–:–
9:17:15 AM: --:–:-- 0
9:17:16 AM:
100 93 100 93 0 0 134 0 --:–:–
9:17:16 AM: --:–:-- --:–:-- 654
9:17:16 AM: 1
9:17:16 AM: 00 630 100 630 0
9:17:16 AM: 0 649 0 --:–:-- --:–:-- --:–:-- 649
9:17:16 AM:
100 1142k 100 1142k 0 0 819k 0 0:00:01
9:17:16 AM: 0:00:01 --:–:-- 819k
9:17:16 AM: [2/2]: https://yarnpkg.com/do
9:17:16 AM: wnloads/1.13.0/yarn-v1.13.0.tar.gz.asc → /tmp/yarn.tar.gz.mZbIin738u.asc
9:17:16 AM:
100 84 100 8
9:17:16 AM: 4 0 0 3055 0 --:–:-- --:–:-- --:–:-- 3055
9:17:16 AM:
100 97 100 97
9:17:16 AM: 0 0 1748 0 --:–:-- --:–:-- --:–:-- 1748
9:17:16 AM: 1
9:17:16 AM: 0
9:17:16 AM: 0
9:17:16 AM: 6
9:17:16 AM: 3
9:17:16 AM: 4
9:17:16 AM: 1
9:17:16 AM: 0
9:17:16 AM: 0
9:17:16 AM: 6
9:17:16 AM: 3
9:17:16 AM: 4
9:17:16 AM: 0
9:17:16 AM: 0
9:17:16 AM: 7
9:17:16 AM: 2
9:17:16 AM: 7
9:17:16 AM: 8
9:17:16 AM: 0
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: :
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: :
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: :
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: :
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: :
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: :
9:17:16 AM: -
9:17:16 AM: -
9:17:16 AM: 7
9:17:16 AM: 2
9:17:16 AM: 7
9:17:16 AM: 8
9:17:16 AM:
0 832 0 0 0 0 0 0
9:17:16 AM: --:–:-- --:–:-- --:–:-- 0
100 832 100 832 0
9:17:16 AM: 0 6194 0 --:–:-- --:–:-- --:–:–
9:17:16 AM: 812k
9:17:16 AM: > Verifying integrity…
9:17:16 AM: gpg: Signature made Tue 18 Dec 2018 04:04:55 PM UTC using RSA key ID B6FF4DE3
9:17:16 AM: gpg: Good signature from “Yarn Packaging yarn@dan.cx”
9:17:17 AM: gpg: Note: This key has expired!
9:17:17 AM: Primary key fingerprint:
9:17:17 AM: 72EC F46A 56B4 AD39 C907 BBB7 1646 B01B 86E5 0310
9:17:17 AM: Subkey fingerprint: E219 30C4 D0A4 AA46 1858 1F7A E074 D16E B6FF 4DE3
9:17:17 AM: > GPG signature looks good
9:17:17 AM: > Extracting to ~/.yarn…
9:17:17 AM: > Adding to $PATH…
9:17:17 AM: > Successfully installed Yarn 1.13.0! Please open another terminal where the yarn command will now be available.
9:17:18 AM: Installing NPM modules using Yarn version 1.13.0
9:17:18 AM: yarn install v1.13.0
9:17:19 AM: warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
9:17:19 AM: [1/4] Resolving packages…
9:17:19 AM: [2/4] Fetching packages…
9:17:44 AM: info fsevents@2.1.2: The platform “linux” is incompatible with this module.
9:17:44 AM: info “fsevents@2.1.2” is an optional dependency and failed compatibility check. Excluding it from installation.
9:17:44 AM: info fsevents@1.2.13: The platform “linux” is incompatible with this module.
9:17:44 AM: info “fsevents@1.2.13” is an optional dependency and failed compatibility check. Excluding it from installation.
9:17:44 AM: info fsevents@2.1.3: The platform “linux” is incompatible with this module.
9:17:44 AM: info “fsevents@2.1.3” is an optional dependency and failed compatibility check. Excluding it from installation.
9:17:44 AM: [3/4] Linking dependencies…
9:17:44 AM: warning “react-scripts > @typescript-eslint/eslint-plugin > tsutils@3.17.1” has unmet peer dependency “typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta”.
9:17:44 AM: warning " > reactjs-popup@1.5.0" has unmet peer dependency “prop-types@^15.6.0”.
9:17:56 AM: [4/4] Building fresh packages…
9:17:57 AM: Done in 39.02s.
9:17:58 AM: NPM modules installed using Yarn
9:17:58 AM: Started restoring cached go cache
9:17:58 AM: Finished restoring cached go cache
9:17:58 AM: go version go1.12 linux/amd64
9:17:58 AM: go version go1.12 linux/amd64
9:17:58 AM: Installing missing commands
9:17:58 AM: Verify run directory
9:17:58 AM: Executing user command: yarn start
9:17:59 AM: yarn run v1.22.4
9:17:59 AM: $ react-scripts start
9:18:01 AM: ｢wds｣: Project is running at http://10.4.13.247/
9:18:01 AM: ｢wds｣: webpack output is served from
9:18:01 AM: ｢wds｣: Content not from webpack is served from /opt/build/repo/public
9:18:01 AM: ｢wds｣: 404s will fallback to /
9:18:01 AM: Starting the development server…
9:18:01 AM: Done in 2.35s.
9:18:01 AM: Skipping functions preparation step: no functions directory set
9:18:01 AM: Caching artifacts
9:18:01 AM: Started saving node modules
9:18:01 AM: Finished saving node modules
9:18:01 AM: Started saving yarn cache
9:18:01 AM: Finished saving yarn cache
9:18:01 AM: Started saving pip cache
9:18:01 AM: Finished saving pip cache
9:18:01 AM: Started saving emacs cask dependencies
9:18:01 AM: Finished saving emacs cask dependencies
9:18:01 AM: Started saving maven dependencies
9:18:01 AM: Finished saving maven dependencies
9:18:01 AM: Started saving boot dependencies
9:18:01 AM: Finished saving boot dependencies
9:18:01 AM: Started saving go dependencies
9:18:01 AM: Finished saving go dependencies
9:18:06 AM: Build script success
9:18:06 AM: Starting to deploy site from ‘’
9:18:06 AM: Creating deploy tree
9:18:06 AM: Creating deploy upload records
9:18:06 AM: 0 new files to upload
9:18:06 AM: 0 new functions to upload
9:18:06 AM: Starting post processing
9:18:06 AM: Post processing done
9:18:06 AM: Site is live
9:18:32 AM: Finished processing build request in 1m24.356020944s

Any advice? Thanks everyone for your help.

[perry]

hey there,

I am not 100% sure i understand what is going on, but i want to bring your attention to this part of the log:

9:18:06 AM: Build script success
9:18:06 AM: Starting to deploy site from ‘’
9:18:06 AM: Creating deploy tree
9:18:06 AM: Creating deploy upload records
9:18:06 AM: 0 new files to upload
9:18:06 AM: 0 new functions to upload

Something funky is going on here, and i don’t think things are set up quite right. Could you share your package.json and also a screenshot of your build settings?

[edlr73]

Basically, I made some updates to my site, and when I run it locally, it looks fine. But after I push it to GitHub, the Netlify Prod deploy it removes any background pictures. Here is my package.json.

{

“name”: “resume”,

“version”: “0.1.0”,

“private”: true,

“dependencies”: {

"react": "^16.13.1",

"react-dom": "^16.13.1",

"react-scripts": "3.4.1",

"reactjs-popup": "^1.5.0",

"yarn": "^1.22.4"

},

“scripts”: {

"start": "react-scripts start",

"build": "react-scripts build",

"test": "react-scripts test --env=jsdom",

"eject": "react-scripts eject"

},

“devDependencies”: {

"ajv": "^6.12.2",

"url-parse": "^1.4.7"

},

“browserslist”: {

"production": [

  ">0.2%",

  "not dead",

  "not op_mini all"

],

"development": [

  "last 1 chrome version",

  "last 1 firefox version",

  "last 1 safari version"

]

}

}

[perry]

sorry its taken us a bit to get back to you on this.

I’m personally wondering if this is some kind of issue with case sensitivity:

Hey there, thanks for reaching out.

What you are describing sounds a bit like a an issue with case sensitivity on our system.

Can you give this a read through and let us know if that fixes the issue?

[Support Guide] Netlify app builds locally but fails on deploy (case sensitivity)

Last Reviewed By Netlify Support Staff: December 2022 Are you struggling to understand why your project runs locally but errors out with missing files or logs that point toward issues with case when you try and build on Netlify? You are not alone. Often, case (as in: UPPERCASE or lowercase letters in filenames or paths) can cause problems. Here is a guide to understanding how case sensitivity issues present themselves, why they arise, and how you can fix them! 1. Errors you might see Case sens…

have you been able to make any progress on this at all?

[edlr73]

My apologies, I’ve been under the weather (I checked with the doctor - NOT Covid-19), so I wasn’t able to check the naming conventions on my files. But you caught it and I relinked the deploy build settings. This line in the deploy details was the issue. It didn’t have my build link.

6:11:24 PM: Starting to deploy site from ‘build’

Thanks for lending an eye, I’m really trying to get out of rookie mode. Onward to developing my site!

[perry]

awesome. glad you are feeling better, glad it wasn’t covid, glad its working!

We love rookies around here - come on back any time and ask as many questions as you need.