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-plugin-transform-skate-flow-props

v0.1.0

Published

> Babel plugin to transform Flow types to Skate props.

Downloads

11

Readme

babel-plugin-transform-skate-flow-props

Babel plugin to transform Flow types to Skate props.

Install

npm install babel-plugin-transform-skate-flow-props

Usage

In your .babelrc:

{
  "plugins": ["transform-skate-flow-props"]
}

Output

This plugin is designed to be used with Skate props, but can be applied to any class deriving from HTMLElement. The output simply assumes that you're using props from SkateJS.

Sample input:

import { props } from 'skatejs';

type Props = {
  name: string;
  tags: Array<string>;
};

class Test extends HTMLElement {
  props: Props
}

Sample output with Flow types stripped and before transforming class fields:

import { props } from 'skatejs';

class Test extends HTMLElement {
  static props = {
    name: props.string,
    tags: props.array
  }
}

Use cases

The major use case of this library is to allow you to simply write Flow without having to duplicate them as Skate props. You get the behaviour and semantics of Skate props and Flow types all in one.

Skate's React renderer

Something we're aiming to support is sharing Flow types between React prop types and Skate props. This means that if you want to wrap your React component with web component (using Skate's React renderer), you can share the Flow types and not have to redefine the props for Skate to get their behaviour.

An example:

// @flow

import React from 'react';
import { props, withComponent } from 'skatejs';
import withRenderer from '@skatejs/renderer-react';

type Props = {
  name: string,
  tags: Array<string>
};

class ReactComponent extends React.Component {
  props: Props;
  render() {
    return <div>{this.props.name}: {this.props.tags.join(' ')}</div>;
  }
}

class SkateComponent extends withComponent(withRenderer()) {
  props: Props;
  renderCallback() {
    return <ReactComponent {...this.props} />;
  }
}

Without this, you'd have to manually write the props on the Skate component like so:

class SkateComponent extends withComponent(withRenderer()) {
  static props = {
    name: props.string,
    tags: props.array
  };
  renderCallback() {
    return <ReactComponent {...this.props} />;
  }
}

This can be super tedious.

On top of trying to make your life easier, we also want to try and bridge the gap between web components and the React component model as much as possible. We think the two are complimentary and should be simple to compose together when necessary.