React app getting File_not_found on js, Access denied on css

Hello, I'm trying to run a nearly new React project that I created using create-react-app, and then I made a build. The problem I'm having is that initially it doesn't take files from the static folder. At first, I tried moving the CSS and JS files to the root directory, and it worked. But now I'm working on a larger project and I need folder structure. Can anyone tell me if they have encountered something similar, and if there is a ready solution?
Screenshot 2024-04-05 083836

Troubleshooting Static File Loading Issues in React Projects Created with Create React App

If you're encountering issues with static files not loading correctly in a React project created using Create React App, you're not alone. This is a common issue that can arise due to misconfigurations or pathing problems. Here’s how you can address this problem while maintaining your desired folder structure.

Why Does This Happen?

Static file loading issues often occur because of incorrect file paths or build settings. When React builds your project, it generates a build folder that contains your static files like CSS and JS. Ensuring these files are correctly referenced is crucial for your application to function properly.

Common Solutions to Static File Issues

1. Correctly Reference Static Files

Make sure your static files are referenced correctly. When using Create React App, your public folder is the root for your static files. Inside your components, you should reference these files relative to the public folder.

// Correct way to reference a file in the public folder
<img src={`${process.env.PUBLIC_URL}/path/to/your/image.png`} alt="description" />

2. Use the Public Folder Correctly

Ensure you place your static files inside the public folder and reference them using the process.env.PUBLIC_URL environment variable as shown above. This approach helps Create React App correctly locate and serve these files.

3. Configure the homepage in package.json

If your React app is not at the root of your domain, you need to set the homepage field in your package.json file. This configuration ensures that your build process correctly sets the paths for your static files.

// package.json
{
  "name": "your-app",
  "version": "0.1.0",
  "private": true,
  "homepage": "http://yourdomain.com/subdirectory",
  "dependencies": {
    // your dependencies
  },
  // other configurations
}

4. Check Your Build Folder

After running npm run build, check the contents of the build folder. Ensure that the static directory contains your CSS and JS files, and that the paths in the index.html file reference these files correctly.

5. Serve Your App Correctly

If you are serving your app from a server, ensure that the server is configured to serve static files correctly. For example, if you’re using Express, you might need to set up middleware to serve static files.

const express = require('express');
const path = require('path');
const app = express();

app.use(express.static(path.join(__dirname, 'build')));

app.get('/*', function(req, res) {
  res.sendFile(path.join(__dirname, 'build', 'index.html'));
});

app.listen(3000);

Conclusion

Static file loading issues in React projects can be frustrating, but with the correct configuration, they are solvable. Ensure your files are correctly referenced, configure your homepage in package.json, and make sure your server is set up to serve static files properly. By following these steps, you can maintain your folder structure and ensure your larger projects run smoothly.

If you continue to experience issues, consider consulting with a React Native development company for professional assistance. Their expertise can help streamline your development process and resolve any lingering problems efficiently.

https://celadonsoft.com/react-native