npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

apex-log-filter

v1.2.1

Published

CLI for filtering USER_DEBUG output from Salesforce Anonymous Apex execution logs

Downloads

1,464

Readme

apex-log-filter

CLI for filtering USER_DEBUG output from Salesforce Anonymous Apex execution logs

Actions Status

When executing Anonymous Apex using sfdx force:apex:execute the logs contain a lot of debug information. If you want to show only the output coming from System.debug() this is the tool to use.

Unlike a simple grep '|USER_DEBUG|' this supports multi-line messages.

Example

Compare the following output from running System.debug('Hello World\nThis is a debug message.'):

48.0 APEX_CODE,DEBUG;APEX_PROFILING,INFO Execute Anonymous: System.debug('Hello World\nThis is a debug message.'); 04:25:21.21 (21632799)|EXECUTION_STARTED 04:25:21.21 (21650642)|CODE_UNIT_STARTED|[EXTERNAL]|execute_anonymous_apex 04:25:21.21 (22596799)|USER_DEBUG|[1]|DEBUG|Hello World This is a debug message. 04:25:21.23 (23123489)|CUMULATIVE_LIMIT_USAGE 04:25:21.23 (23123489)|LIMIT_USAGE_FOR_NS|(default)| Number of SOQL queries: 0 out of 100 Number of query rows: 0 out of 50000 Number of SOSL queries: 0 out of 20 Number of DML statements: 0 out of 150 Number of DML rows: 0 out of 10000 Maximum CPU time: 0 out of 10000 Maximum heap size: 0 out of 6000000 Number of callouts: 0 out of 100 Number of Email Invocations: 0 out of 10 Number of future calls: 0 out of 50 Number of queueable jobs added to the queue: 0 out of 50 Number of Mobile Apex push calls: 0 out of 10

04:25:21.23 (23123489)|CUMULATIVE_LIMIT_USAGE_END

04:25:21.21 (23171269)|CODE_UNIT_FINISHED|execute_anonymous_apex 04:25:21.21 (25341413)|EXECUTION_FINISHED

Installation

$ npm install -g apex-log-filter

Usage

$ echo "System.debug(UserInfo.getUserName());" | sfdx force:apex:execute | apex-log-filter
[email protected]

Sponsors

License

MIT © Matthias Rolke