Search Results for "apache module"

Lighthouse is an open-source, automated tool that analyzes and audits web apps and web pages in order to improve their quality. Lighthouse collects modern performance metrics and insights on developer best practices; auditing for performance, accessibility, SEO and more. After auditing it produces a report either in JSON or HTML. Included in the report is a reference doc that explains the importance of the audit and how to fix the problem areas, which you can use to improve the web app or...

App size is an important metric which directly correlates with business metrics like install conversion rate. Measuring app size is straightforward, but knowing what contributes to it is not. Especially in bigger projects with hundreds or thousands of modules and third-party dependencies. Ruler provides a convenient way to find out how much each module and dependency contributes to the total size of your app by running a single Gradle task. First you need to add the Ruler Gradle plugin to...

ByteX is a bytecode plugin platform based on Android Gradle Transform Api and ASM. (Maybe you can think of it as a socket with unlimited plugs?) In the apk building process, each plugin is completely independent. It not only can run independently from the ByteX host, but also can be automatically integrated into the host into a single Transform along with other plugins. What's more, each plugin's code is decoupled from one another, as well as their host, which makes it extensible and highly...

An sbt plugin enhancing the evicted key. sbt has been gradually providing these features. As of sbt 1.5.0, all of the features of this plugin are now supported by sbt out of the box. Nevertheless, this plugin can be useful if you are stuck with an old version of sbt. Unlike the default evicted task, the eviction warnings task reports only problematic evictions (ie, libraries that have been evicted by binary incompatible versions). This task turns the eviction warnings into errors. It...

When I was learning Haskell, I missed the nice features of IntelliJ IDEA. My first approach was to use the default way of creating an IntelliJ plugin by defining a grammar and a lexer according to Haskell report. That didn't work out because I could not define all the recursion. Then I decided to use grammar and lexer definitions only for tokenizing and parsing Haskell code, and not for syntax checking the code. This is needed for syntax highlighting, all kinds of navigation, and so on....