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

glamor-plugin-detect-component

v0.2.0

Published

Glamor plugin. Detects and displays component where style was defined.

Downloads

3

Readme

glamor-plugin-detect-component

Install

npm install -S glamor-plugin-detect-component

Usage

import { plugins } from 'glamor'
if (process.env.NODE_ENV == 'development') {
  const extractToComment = require('glamor-plugin-extract-to-comment').default
  const detectComponent = require('glamor-plugin-detect-component').default

  plugins.add(extractToComment('GlamorComponent', true))
  plugins.add(detectComponent())
}
const App = require('./components/App').default

This plugin detects component where style is defined and adds it's name to 'GlamorComponent' style property. It will show up as -glamor-component in final stylesheet.

Detection is done via stack trace. By default only file name is used. You can pass formatter function to configure it. Default implementaion is:

plugins.add(detectComponent((fileName, functionName) => {
  const match = /([^/]*?)(?:\/index.js)?\??$/.exec(fileName)
  return match ? match[1] : null
})

It is best to use glamor-plugin-extract-to-comment plugin for better readability. In snippet above it extracts GlamorComponent and removes it from style object. Take a note that glamor plugins execute in reverse order. Last added plugin will run first.

Chrome Canary

Latest version of Chrome Canary implements tail call optimization. It prevents component detection for root elements of your components.

If your setup is basen on this instructions, you can disable optimization with this trick in .babelrc

"env": {
  "development": {
    "plugins": [
      [
        "transform-react-jsx",
        { "pragma": "Glamor._NIL=Glamor.createElement" }
      ]
    ]
  }
}

Glamor._NIL is just a random identifier. Key is to add assignment of function result to prevent optimization.

It will render to weird but correct code:

var App = function App() {
  return Glamor._NIL=Glamor.createElement(
    'div',
    _extends({ css: css }, (0, _glamor.hover)({ color: 'red' })),
    Glamor._NIL=Glamor.createElement(_OtherComponent2.default, null)
  );
};

Supported browsers

Tested in Chrome Canary and Firefox. Feel free to file an issue if it does not work in a browser you need to use in development.

License

MIT © Vladimir Danchenkov