meelash / mundlejs Goto Github PK

Phantomjs-node is not working with node >0.10.3: https://github.com/sgentle/phantomjs-node/issues/77

phantomjs doesn't have function.prototype.bind: ariya/phantomjs#10522

When both of these are cleaned up, make sure the testListen.clientServed test works.
Wonder if there's a way I can pass by it so it doesn't have to be commented out for all the other tests to run?

I want to include compiled jade templates in my client-side js. How awesome will that be? Widgets and all, just concatenated in... sweet.

Also, I want to use coffeescript.

We need some load tests so that we can compare different options for serving files, e.g.:

I know we shouldn't be converting buffer->strings unless absolutely necessary on account of the cpu cost,
we need to experiment with cdn integration,
we need to quantify how much different cacheing strategies improve performance.

This can happen, for example, if the first require ever doesn't have a callback or if there's a require with no callback and a variable instead of string argument passed to it.

scripted looks like it might be a good choice: https://github.com/scripted-editor/scripted

Uses requirejs, so code should be fairly modular and easy to convert
Served from node.js
Nice, big application, looks like >2MB unminified javascript served

The only possible con about it is that I'm not sure it has much room for demoing async loading. If there was an app with lots of different windows, etc. it might be better... But maybe stuff like save/open dialogs and all could be loading async?

Packages, like npm, cpan etc.

mundle install [email protected]

Should be relatively easy to implement, but very, very cool.

Real client-side package management.

Wonder if it would be beneficial to be able to deploy to cdn. The way it could work is, as bundles are cached on the server, they could be uploaded to a cdn. The next time a client connects, the client-side code can include the location of that bundle. The client-side code can also be included on a cdn and be updated there with the latest cache.

Seems like the biggest challenge is working with the api to different cdn's. Need to research if they even exist and if there is any standardization.

pre-cache dependency trees and other pre-runtime optimizations

Errors passed to the client such as file not found

Bit of a pipe-dream at this point, but the client-side package management idea got me thinking of the possibilities :)

cross-language/environment client-side package support.

g-wan would be very cool, perl, ruby, etc.

The failure modes are different for async and sync requires of an unauthorized file (below the 'root' directory).

Instead of just making the module contain an empty string, actually store the error in the module and show it every time that is required