Todo list component example app:
Installation
Of course have component(1) installed:
$ npm install -g component
Install express for the server, and the component dependencies:
$ npm install
$ make
Running the app
$ node app
Implementations
This repository has several branches to display several techniques that may be applied to structure your application. So far we have the following:
- `master` uses separate `./client` and `./server` directories
- `single` uses a single `./lib` directory to house both server and client components
- `multiple` uses domain-specific directories `./lib/{models,controllers,views}`
Implementation
In this implementation all private client-side components are located in ./client,
while server related REST end-points are in ./server. The ./index.html
file bootstraps the client-side, and app.js is a small Express server
to power the backend.
Each client-side component in ./client defines its own dependencies,
both "local" (in the ./client dir), and remote from public components
that devs have created. On make these are installed and the builder
outputs ./build. The tiny 1-line middleware in ./server/build executes
make on-demand each time index.html is requested, so you don't even
have to know about the build
This is just one example of how you could structure an application. You could
for example take a more traditional approach with ./models, ./controllers,
and ./views etc. The entire app could be a single component, with all dependencies
specified in the root ./component.json, however I recommend splitting your app
into multiple as shown here, regardless of directory structure.
Components used
- page.js for routing
- model for models
- collection for model collections
- keyname for keycode name strings
- reactive for reactive templates
License
MIT