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

copy-paste-component

v2.0.4

Published

A tool to create components, by copying and pasting existing ones.

Downloads

5

Readme

copy-paste-component

travis appveyor codecov npm downloads npm version PRs Welcome styled with prettier

A tool to create components, by copying and pasting existing ones.

Usage

If you have the structure below:

src/components/App/App.js
src/components/App/App.test.js
src/components/App/App.stories.js
src/components/App/index.js

and run the tool, it will create the following structure, replacing occurrences of the word App inside the files to NewApp:

src/components/NewApp/NewApp.js
src/components/NewApp/NewApp.test.js
src/components/NewApp/NewApp.stories.js
src/components/NewApp/index.js

Installation

yarn global add copy-paste-component or npm i -g copy-paste-component

Editor integration

Are you looking for an editor extension? Check the ones available:

Usage

On the root of your project, run cpc or copy-paste-component.

It will prompt you three questions:

  • Which component would you like to copy?
  • What is the name of the new component?
  • What is the location of the new component?

When you answer those questions, it will generate a structure that is the same as the one that the selected component uses, but it will change the filename to the one you provided on the second question. It will look too inside the file for occurrences of the filename, and if it finds, it replaces with the content of the second question.

So, given the following file:

App.js

import React from 'react'

const App = () => <div>Hello World</div>

export default App

Becomes the following:

NewApp.js

import React from 'react'

const NewApp = () => <div>Hello World</div>

export default NewApp

There is also an option to skip the questions, providing them directly when you call the package, using the copy command, like cpc copy src/components/App/App.js NewApp src/components/NewApp. The first argument is the path of the component you want to copy, the second is the name of the new component, and the last one is the path where the component will be created.

Roadmap

See Roadmap

Changelog

See Releases

License

MIT