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

babel-jsx-utils

v1.1.0

Published

Utilities for working with Babel and JSX

Downloads

783,220

Readme

babel-jsx-utils

This library allows you to resolve the actual values of attributes when parsing JSX with Babel. This is useful for things like Babel plugins. It evaluates the value in the local scope, so local variables are ok, but properties passed to the component are not.

For example:

// OK
export function Logo() {
    const src = "trex.png";

    return <img src={src} alt="T-Rex" />;
}
// Not OK
export function Logo({ src }) {
    return <img src={src} alt="T-Rex" />;
}

It can handle expressions, but not function calls:

// OK
export function Logo() {
    const width = 100 * 2;

    return <img src={"trex.png"} width={width} alt="T-Rex" />;
}
// Not OK
export function Logo() {
    function double(value) {
        return value * 2;
    }

    const width = double(100);

    return <img src={"trex.png"} width={width} alt="T-Rex" />;
}

Installation

Install:

yarn install babel-jsx-utils

or

npm install babel-jsx-utils

Usage

import { parse, traverse } from "@babel/core";

const ast = parse(`<Foo bar="hello" />`, {
    filename: "foo.js",
    presets: ["@babel/preset-react"],
});

traverse(ast, {
    JSXOpeningElement(nodePath) {
        const values = getAttributeValues(nodePath);
        // values = { bar: "Hello" }
    },
});

For more examples, see the tests

API

/**
 * Get all attribute values of a JSX element. This only includes values that can be
 * statically-analysed. Pass the `onError` callback to be notified if an attribute cannot be resolved.
 *
 * @param nodePath The NodePath of the JSX opening element
 * @param onError Called with the attribute name if it is present but cannot be resolved
 * @param include If present, only these props are evaluated. Does not apply to spread attributes.
 */
export declare function getAttributeValues(
    nodePath:
        | CoreNodePath<JSXOpeningElement>
        | TraverseNodePath<JSXOpeningElement>,
    onError?: (attributeName: string) => void,
    include?: Set<string>
): Record<string, any>;
/**
 * Attempt to get the value of a JSX attribute. Returns an object with the
 * properties `confident`, which is false if the value cannot be resolved
 * in the current scope, and `value` which is the value if it can be.
 *
 * If the attribute is empty, then the returned value is `true`, e.g.
 * `<Image eager />` would return `true` for the `eager` attribute.
 *
 * @param nodePath The NodePath of the JSXAttribute
 */
export declare function getAttributeValue<T = unknown>(
    nodePath: CoreNodePath<JSXAttribute> | TraverseNodePath<JSXAttribute>
): {
    confident: boolean;
    value: T | true;
};