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

mithril-source-hint

v1.1.0

Published

Find file where domnode was created

Downloads

5

Readme

mithril-source-hint

test

With a growing Mithril app, you (or your coworkers) may sometimes wonder, where a specific DOM element comes from.

This little packages allows you to show the origin of any element by just hovering it.

Installation

npm install --save mithril-source-hint

To make use of it, you need to change all your files to use a custom Mithril wrapper, that - as a nice goodie - allows you to toggle hints by URL parameter. In the following example, we use ?mdebug for as url parameter:

'use strict'

// by default we keep Mithril itself
module.exports = require('mithril')

// wrap Mithril if we add ?mdebug to the url
if (window.location.search.indexOf('mdebug') > 0) {
  module.exports = require('mithril-source-hint')
}

To update all your require statements to use your custom Mithril wrapper, you may use something like that in your application's root directory (your wrapper is probably not named my/mithril, so you need to change that):

for js in `find . -type f -name '*.js'`; do sed -i s@require\(\'mithril\'\)@require\(\'my/mithril\'\)@g $js; done

Usage

Call your site (with the URL parameter, if you require it in your wrapper). Hover a element, you want to see the origin of, and you will see file and line of it as title.