Pre:ClojureRemote 17 — Feathers.js Server (cljs (feathers))
Now we can really dive into the feathers server. We are basing this server on the feathers-chat demo. A quick read through of the chat server shows that we will need a few more namespaces for interacting with other feathers components. We will also need to interact with the Node.js API, and a few third-party libraries as well.
If you want to walk through building the chat application, grab tickets to ClojureRemote 17:
To make FeatherScript even more awesome, we are going to wrap the feathers-configuration package and provide an easy way to generate config files from boot or the project directory. From here we will also wrap the third-party packages which are commonly used by feathers. These include body-parser, CORS, compression and serve-favicon.
CLJS doesn’t have any type of API for running on Node.js and really everything is available through inter-op anyway. They do provide us with the “require” function which is all we need to get started. I have made a publicly available nodejs-cljs package which makes things feel more clojure-ish, and avoids all the extra js inter-op dots, feel free to extend it.
If you want to report issues, all the work being done for ClojureRemote can be tracked here:
Here we restart our boot build and fix any namespace issues. (We only had a few warnings to resolve)
