-
Notifications
You must be signed in to change notification settings - Fork 5
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
Can you provide any larger examples of Kevin in the wild? #6
Comments
Hey, I'm glad you're interested in Kevin! I have a bunch of questions.
|
Hey @salemhilal
Added |
Hey @erlandsona, thanks so much for providing examples — super helpful! Thanks for catching the syntax error in the Now on to answers: I threw together a quick example of Kevin being used to manage multiple compilers. You can take a look here. Something to clear up — Kevin is meant as an analog to When using Kevin as in your provided code, your server won't be serving any HTML — only JavaScript, so it kind of makes sense that you'd get a 404 by visiting the root route. In order to serve your HTML, you'll need to add an express static middleware after the Kevin middleware. You can see an example of this in the README (where we do Happy to continue advising as you get this in a more workable state for yourself. As you go forward, to get the full benefit of Kevin, you'll want to split your config up into multiple configs, each of which is responsible for building entrypoints just for a portion of your app. |
Wanted to say thank you so much for your response. |
Thanks for the example @joebeachjoebeach! I was slightly confused about how these webpack configs worked and seeing that example cleared it right up. I started building a similar middleware for our project and found this. Great stuff. Thanks! |
I'm trying to spin up kevin as a proof of concept for our client and running into... after following the example... not really sure how to resolve.
I read the article you posted and thought Kevin would be a great fit for our codebase as well. We've got about 3500 js files and webpack-dev-server takes anywhere from a minute or so to build on first launch and about 10-12 seconds for a given change in watch mode.
So the promise of being able to incrementally build portions of the app to speed up development time for a monorepo seems like a very promising solution for our needs as well.
The text was updated successfully, but these errors were encountered: