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

turbine

v0.1.1

Published

Relay-like REST-friendly Immutable-based React data library

Downloads

32

Readme

Turbine

Circle CI Code Climate Test Coverage bitHound Score

Relay-like REST-friendly Immutable-based React data library

[Work in progress]

Getting started

  1. npm install turbine

Usage

Turbine's usage with components is similar to Relay.

import React, { PropTypes } from 'react'
import Turbine, { graphql } from 'turbine'

const AssetsView = React.createClass({
  propTypes: {
    assets: PropTypes.array.isRequired
  },

  render() {
    // ...
  }
})

export default Turbine.container(AssetsView, {
  queries: {
    assets: graphql`
      {
        assets(album_id: <album_id>) {
          id,
          url
        }
      }
    `
  }
})

Warning: Format of the query may be changed in a future release.

<album_id> is a query parameter that can be resolved from props passed by the parent component: <AssetsView album_id="abc" />.

Query params

You can also have query params that are owned by of the component itself. For example, if your component renders a list of items, the number of items can be updated when user scrolls. Use queryParams and setQueryParams:

var AssetsView = React.createClass({
  render() {
    return (
      <div>
        { this.props.assets.map(asset => <img src={asset.url} />) }
      </div>
    )
  },

  loadMore() {
    var count = this.props.queryParams.count
    this.props.setQueryParams({  // <- update queryParams
      count: count + 30
    })
  }
})

module.exports = Turbine.container(AssetsView, {
  queryParams: {  // <- default queryParams
    count: 30
  },
  queries: {
    assets: graphql`
      {
        assets(album_id: <album_id>, count: <count>) {
          id,
          url
        }
      }
    `
  }
})

Models

assets in the graph query above is a bit of magic. Turbine translates the name to Asset, and for things to work, you need to register the Asset model with Turbine. You'd typically do this in your entry module:

Turbine.init({
  models: {
    'Asset': Asset
  }
})

Turbine expects each model to have query, find, create, update, delete/remove methods. It's recommended to use Immutable records as your models:

export default class Asset extends new Immutable.Record({
  // define attributes with default values
  id: null,
  url: ''
}) {
  // define methods
  static query(params) {
    return new Promise(...)
  }
}

Development

  1. Fork the repo
  2. git clone [email protected]:[yourname]/turbine && cd turbine && npm i
  3. Work your magic...
  4. Be sure you have no linting warnings/errors and tests pass.
  5. Push and open a pull request.

Linting

npm run lint

Note: It's recommended to install eslint plugin into your code editor.

Testing

npm test

or continuously

npm i -g karma-cli
karma start

License

(c) 2015 Chute Corporation. Released under the terms of the MIT license.