@kylesloper @hrishikesh any thoughts on why the site would build but the public folder doesn’t seem to hold any content?
Since you and @kylesloper seem to have access to the repo, try building a production (not the development build) once locally and see what you get. Maybe the publish path is different?
Here’s what I see when I run npm run build locally:
OverDawgData@0.1.0 build C:\Users\mlooff\Documents\GitHub\OverDawgData-1
react-scripts build
Creating an optimized production build…
Compiled with warnings.
./src/components/sections/FeaturesSplit.js
Line 179:7: ‘img02Style’ is assigned a value but never used no-unused-vars
Line 187:7: ‘img03Style’ is assigned a value but never used no-unused-vars
./src/views/Home.js
Line 2:8: ‘HeroSplit’ is defined but never used no-unused-vars
Line 3:8: ‘Clients’ is defined but never used no-unused-vars
Line 5:8: ‘FeaturesTiles’ is defined but never used no-unused-vars
Line 6:8: ‘Pricing’ is defined but never used no-unused-vars
Line 7:8: ‘Cta’ is defined but never used no-unused-vars
Search for the keywords to learn more about each warning.
To ignore, add // eslint-disable-next-line to the line before.
File sizes after gzip:
72.02 KB build\static\js\2.d5132f8a.chunk.js
33.57 KB build\static\js\main.ad676e72.chunk.js
10.39 KB (+7 B) build\static\css\main.f6f449f5.chunk.css
784 B (+6 B) build\static\js\runtime~main.47592f47.js
The project was built assuming it is hosted at /build/.
You can control this with the homepage field in your package.json.
The build folder is ready to be deployed.
Find out more about deployment here:
C:\Users\mlooff\Documents\GitHub\OverDawgData-1>
Is there a next step after this? @kylesloper
I am happy to give you access to the repo, if that would help troubleshoot?
Sure. That would help.
However, it looks like your publish path is build and not public. Maybe try that?
1 Like
That worked! Thanks!