Feature (or design) Request: Server-side plugin design

[censys-git]

I am trying to get Less.js to work server-side in a Software as a Service environment. Basically, you are running client side JavaScript on the server without window or DOM (document) objects available. Access to files and directories is through APIs (e.g. createFile, loadFile, saveFile, and so on) and I am having a very difficult time separating out the file accessing/writing portions of the code from the essential less parsing portions. It appears the Rhino version comes the closest to being usable (versus Node.js) since it removes the window/document and AJAX dependencies.

Wondering if it were possible to separate out the two primary sections (file operations and parsing operations) so we could easily plug in our own file operations). Essentially break out any read or write operations into an API.

I can do this myself through trial and error but maintaining would be difficult over time and those closest to the code may know how to do this in a heart beat and once done will allow updates to work without mucking with the code each time.

[matthew-dean]

@lukeapage Duplicate of #1732? (How do you want to track this?)

[lukeapage]

This work is in progress on the 2.0 branch. Closing as we have issues to cover it. Please feel free to comment on the 2.0 pull request and make pull requests to the 2.0 branch.