-
Notifications
You must be signed in to change notification settings - Fork 110
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
Custom paths #382
Comments
Hey, @bkniffler - what's your use case? |
I'm making a package that I use in all of my projects. The package defines the server/client entry points to setup apollo, react-router, styled-components etc, so that the project only needs to have an "app" folder that contains the actual universal react app and optionally a "server" folder to add an API. |
Is there any reason not to allow customizing the paths or add more folders to chokidar (#386, test currently fails unfortunately)? |
Any thoughts? I really try to love kyt (it works great!) but being forced into this structure (src/server, src/client) is a big downer! |
Hey,
Is there any reason why the paths (clientSrcPath, serverSrcPath, ...) can't be modified? What would it take to add them to kyt.config.js?
Of course its possible to just overwrite the webpack config to customize the entry paths, but maybe it'd still be better to expose an API to change essential paths.
edit:
Hmm, I'm not getting too far by overwriting the webpack config, since hot reloading of the server relies on the serverSrcPath that is calculated in the paths.
The text was updated successfully, but these errors were encountered: