Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
.env.production not applied
See original GitHub issueAfter updating from craco 3.6.0 to 4.0.0, I noticed the PUBLIC_URL env variable ( set in .env.production ) is not applied anymore (although there’s a message at the end of the build indicating the correct one => The project was built assuming it is hosted at /PUBLIC_URL).
The issue is quite similar to this one : https://github.com/sharegate/craco/issues/58.
I tried to look at the commits between 3.6.0 & 4.0.0 but couldn’t find where the problem comes from 😕
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Fix with 5.2: https://www.npmjs.com/package/@craco/craco/v/5.2.0
Hi @LentnerStefan
Thank you for reporting the problem.
I am also surprised that the changes affect this. I will have a look soon.
Patrick