Hi Alex, first of all thank you for your feedback!

I assume you’re referring to the difference between what’s written in the how-to section and my rsocket-demo repository; if this is the case please note that the demo application explained in the article is slightly different from the rsocket-demo on github (eg. the rsocket-demo relies on Redis and as you already noticed, might have some other minor differences in directory structure and the like).

The location of the index.js file when this is browserified is not important as long as the result file is moved to a directory which is valid for Spring WebFlux to expose static/public resources. The original index.js file could even be deleted after the browserify operation, and is in fact kept in the rsocket-demo just for dev purposes but wouldn’t be needed for deploy or production.

Thank you again for your contribution and sorry for the confusion :)