Can you provide any larger examples of Kevin in the wild?

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.

:9275/:1 GET http://localhost:9275/ 404 (Not Found)
localhost/:1 Refused to load the image 'http://localhost:9275/favicon.ico' because it violates the following Content Security Policy directive: "default-src 'none'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

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.

[nvanselow]

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!

[erlandsona]

Wanted to say thank you so much for your response. I brought it up in our architecture meeting and we seem to think this would require more structural changes to implement. Those same changes should lead to webpack’s hot realoading being able to handle file changes more gracefully. After which, kevin-middleware might serve us better. But due to the fact that we generate our HTML from webpack and it sounds my team agrees our issue is more structural we’re gonna pursue a light re-structuring first then maybe come back to this.