Skip to content
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

Open
bkniffler opened this issue Feb 8, 2017 · 4 comments
Open

Custom paths #382

bkniffler opened this issue Feb 8, 2017 · 4 comments

Comments

@bkniffler
Copy link

bkniffler commented Feb 8, 2017

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.

@bkniffler bkniffler reopened this Feb 8, 2017
@delambo
Copy link
Member

delambo commented Feb 14, 2017

Hey, @bkniffler - what's your use case?

@bkniffler
Copy link
Author

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.

@bkniffler
Copy link
Author

Is there any reason not to allow customizing the paths or add more folders to chokidar (#386, test currently fails unfortunately)?

@bkniffler
Copy link
Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants