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

log-editor

v0.1.0

Published

[![NPM version](https://img.shields.io/npm/v/log-editor?color=a1b858&label=)](https://www.npmjs.com/package/log-editor)

Downloads

16

Readme

log-editor

NPM version

Fan of using console.log to debugger? Use your editor to inspect the log instead of scrolling the congested terminal.

- console.log(largeObject)
+ console.logEditor(largeObject)

Install

Only works in Node.js environment.

npm i -D log-editor

Add the following statement at the very beginning of your script:

// inject to `console`
import 'log-editor/console'

Then use console.logEditor instead of console.log whenever you want to see the result in editor. It will launch the corresponsing editor powered by launch_editor.

console.logEditor(largeObject)

or directly import without injection

import { logEditor } from 'log-editor'

Options

Named log

Pass a second argument to specify the key. When calling same key for multiple times, the same temp file will be used and overrides the previous content.

console.logEditor(largeObject, 'foo')

To accumulate the result of multiple calls, setting the override to false.

console.logEditor('message 1', 'key', { override: false })
console.logEditor('message 2', 'key', { override: false })

File Extension

By default, log-editor will use log or json as the temp file's extension. You can change it by passing extension in the options so your editor could provide proper syntax hightlight for you.

const code = `import 'log-editor'`

console.logEditor(code, 'code', { extension: 'ts' })

console.logEditor({ foo: 'bar' }) // will auto infer to use `json` as extension
console.logEditor('bar') // will use `log` as extension

Sponsors

License

MIT License © 2021 Anthony Fu