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

react-presentational

v1.6.0

Published

Create direactory and files for a presentational component

Downloads

24

Readme

react-presentational

Coverage Status

Simple module to create basic prescentational component for project. In case you are using concept of containers and components in your project, there's too much basic structure that you need to create over and over. This module tries to reduce that wasted effort.

NOTE: This module is opinionated. It assumes you are using react-css-modules.

Plus you are following the concept of containers and components to manage your code base for React.

For testing Jest is used along with Enzyme

Setup

npm i react-presentational -g

or

yarn global add react-presentational

How to use

Lets assume this is the directory structure of your project

app
  |- components
    |- Card
    |- Rating
  |- containers

Lets assume, we want to create a component named Badge.

Using CLI

Go inside the components directory from your terminal and type this command react-presentational Badge

Options

react-presentational -n componentName [options]

Basic configuration:
  -n, --name  Name of the component
  --flat      Create files at CWD. No directory is created

Using module system

const reactPresentational = require('react-presentational');
reactPresentational('Bagde');

What happens after command is executed?

New directory structure would be:

app
  |- components
    |- Card
    |- Rating
    |- Badge
      |- index.js
      |- Badge.js
      |- Badge.spec.js
      |- Badge.css
  |- containers

This command created 1 directory and 4 files within that directory. Below is the sample content of these files

Badge.css

.sample {}

Badge.js

import React, { PropTypes } from 'react';
import './Badge.css';

const Badge = (props) => {
  return (
    <div styleName="sample">Badge</div>
  )
};

Badge.propTypes = {
};

export default Badge;

Badge.spec.js

import React from 'react';
import { shallow, mount, render } from 'enzyme';
import Badge from './Badge';

describe('Badge test', () => {
  it('should render component', () => {
    const wrapper = shallow(<Badge />);
    expect(wrapper.find('.Badge').length).toBe(1);
  });
});

index.js

import Badge from './Badge';

export default Badge