Want to see pretty graphs? Log in now!
npm install joopl-analyzer
|4||downloads in the last week|
|42||downloads in the last month|
|Last Published By|
|Version||1.1.3 last updated 23 days ago|
|Dependencies (9)||colors, commander, esprima, js-beautify, q, underscore, walk, watchr, path|
Welcome to jOOPL Analyzer !
First of all, thank you for your interest on jOOPL and this analyzer tool.
That "moduleinfo.js" file will contain some kind of metadata that will let jOOPL load the required source files to the Web browser to work with some given class or a group of classes.
Basic usage how-to
jOOPL analyzer should be installed globally using npm:
npm -g install joopl-analyzer
Once it's installed, it can be executed globally in your shell environment.
the analyzer will start from current directory in your shell session.
A concrete base directory will be provided calling the command this way:
joopl-analyzer --directory ./src joopl-analyzer --directory c:\myproject
Again, thank you for your interest. Feedback will be appreciated. Please send it to:
And issues should be added in the GitHub repository:
About the author
jOOPL and jOOPL Analyzer is a project developed by Matías Fidemraizer. You may contact me either in GitHub or LinkedIn:
1.1.3Bugfix: When detecting if instances coming from a derived class had some dependency yet to be added, if there were no dependencies, analyzer was throwing errors.
1.1.2Bugfix: Problems when detecting instances class members in class hierarchies.
- Include support. Now analyzer supports including other moduleinfo.js from other analysis. This enables different frameworks to reference and automatically include third-party dependencies! Documentation will be updated soon to reflect this new feature.
- Now all parameters must be passed to the command-line using CLI arguments and "joopl-analyzer.json" configuration file gets absolutely deprectated.
- In some cases, new instances weren't detected. It was an error executing some regular expression. Now this has been fixed.
- Previous version introduced a bug: classes deriving built-in jOOPL classes produced an error during detection.
- Dependencies in few cases weren't detected in the right order in very few cases.
- Dependencies from more than a class hierarchy level were not detected.
- New class instances from non-imported namespaces were parsed and this situation caused output errors. Now these are not parsed anymore as expected.