-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Add public folder after eject from 0.2.2 #938
Comments
You can revert the commit when you ejected, then apply migration instructions in the changelog from the old version to the one you need, and then optionally eject again. |
Thanks for the tip. I will try and revert commit even tho we did a lot of changes to build to also deploy for us. ps. and offtopic: Gaearon thanks for all your work and efforts to help the community I have personally learned a lot from you!!! |
If it's too hard to reapply changes, you can try following what was done in #703. |
I have actually did manage to do it after checking the new build file. Added appPublic and AppBuildPublic to paths.js
Added
Is this a proper quick solution @gaearon ? welcomed with any suggestions. |
For this to work in development, you'd also want to include the public folder into |
(I'll close as this isn't an actionable issue for us.) |
Hey guys,
I have started a project a couple of months ago (react-scripts 0.2.2) and now because I will be deploying to production and our partners are very skeptical about cdn's I am using. I want to create a public folder.
Can you guys give me a hint how to add that one?
I checking the new version of create-react-app and ejecting and checking the code differences.
The text was updated successfully, but these errors were encountered: