How To Start
npm install to bring all dependencies in, then
npm run build whenever you change assets or simply
npm run watch to automatically update all new files.
To test the example page, just run the usual
- cdn contains all optimized on-demand static assets. It's automatically managed, nothing to do there.
- public is the actual public site content. It contains few static assets but also JS bundles. You can add CSS bundles too (coming soon).
- viper is where the actual app code is defined, it has at least these subfolders: client, for the browser related client-side code, server, for the HTTP based back-end service, and view, for the external files used either on the client, on the server, or in both, to generate the whole page, or partial content.
You can surf each folder inside ./viper one to know more about each role.
- can I use express or others? Sure you can, this is just a basic setup.
- how to cleanup tinyCDN cached content? You can simply
rm -rf cdn/*or
npm run purgebefore re-deploying. tinyCDN gives for granted if a file name is the same, the content must be too. It really works in that sense.
- how come the example page shows with hiccups? It's a demonstration that viperHTML can also render partial asynchronous chunks, no matter in which order these are resolved. You can remove the array of promises from the
bodyinfo of the server
modeland re-test anything you'd like to