Consider renaming `src` directory to `client`

[richb-hanover]

I realize that this train may have left the station/horse out of the barn/etc. but...

Would you consider renaming the src directory to be the client directory? Or allowing client to alias to src?

The major reason I want this is that I immediately needed to create a server directory to handle the proxied queries (thanks for shipping 0.2.3!), and now my project has two major folders: server and the not-quite-complementarily-named src.

Not a big deal, I can clearly live with it. But you're doing great work for the React/Javascript/etc. beginner's ecosystem, so this would make things a bit easier for newbies...

[lacker]

I think this horse is out of the barn and well on its way into the next county. Are you sharing code between client and server? If so, you might just want to put your server code inside src. But if you're not sharing code between client and server, you might just want your server code to go in a separate directory entirely, rather than being a subdirectory of your create-react-app app.

[steida]

I can only recommend this structure https://github.com/este/este/tree/master/src It would open a lot of possibilities.

[richb-hanover]

Two useful suggestions. Consider my proposal withdrawn. Thanks!

[marienfressinaud]

I actually have a similar problem: my backend is written in Go and frontend has been created with create-react-app and both are in the same repository. It makes me uncomfortable to have frontend in a src folder since it could contain backend too… which is not the case.

My actual folders' structure is the following:

- [Go-specific files]
- ./client
    - ./src
    - package.json
    - index.html

Problem is when deploying on Heroku for instance, it does not detect my package.json file so I had to write a small script which package the app on my PC and push all of that on Heroku. It's working but it could be a bit more elegant :).

I know it's a quite specific problem so I don't ask to reconsider this issue, but do you have an already-working and more elegant solution?