Home

Welcome to the UglifyJSMonitor wiki!

There are a few things that have to be put together.

• The project setup
• Tools to automatically fetch uglifyJS, do some tests and store results
• Tools to display the results on a site

To be honest, I don't know completely yet how this can all be accomplished. And this will probably take some time. The site will probably run on something similar like express. The background tasks could run once a day or less (depending on how long it takes to run the tests). The results should be rendered using a tool (maybe we can use the google graph api or similar).

Rules

A project like UglifyJS is quite big, a consequence of this is that there will be always bugs, typos, lack of features or mistakes. While small mistakes are obvious, bugs and new features can be complex or may involve other complications.

Therefore, it's advised not to use this tool for begging. Beggars will end up making these features themselves which may or may not be helped by others. Some things aren't that simple and take time to understand and correct.

TODO

• Deciding which part of the project shall be public and which may be private. Frontend stuff is probably going to be public, and so will be the tester. Background thread may be held private for now.

Meh, I just try to keep as much things public when I can if it involves code. Logs are kept private.

• Set up prototype. (Actually, everything needs to be rewritten in specs so there will be less clutter in the codebase)

• Every step is a huge step forwards and should be indicated as such. Regressions are important as well. The goals should never be to reach 100% in the least possible time possible.

Project todo

• Maybe set up own test262 runner. This might speed up testing and get more reliable information. It will require some maintenance but we'll see how it goes.