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

st-cp

v2.0.0-beta.2

Published

CLI tool for platform independent, recursive copying of files and folders.

Downloads

28

Readme

st-cp

Gitter

Node CI

Cross-platform cp copy easy files and folders: create missing folders automatically

use it programmatically: install via npm i st-cp or yarn add st-cp.

import {copyPathOrFile} from 'st-cp';

copyPathOrFile('sourcePath',{path: 'destinationPath', isDirectory: true});

use the cli npx st-cp source destination

Parameter

source

  • required
  • multiple (files and folders)

destination

  • required

  • enforce folder with / @ the end

Examples:

copy files to a folder

 # before
 ├── --- file1
 ├── --- file2
 ├── --- file3

st-cp file1 file2 file3 folder

 # after
 ├── --- file1
 ├── --- file2
 ├── --- file3
 ├── --- folder/file1
 ├── --- folder/file2
 ├── --- folder/file3

copy file to a folder

 # before
 ├── --- file

st-cp file folder/

 # after
 ├── --- file
 ├── --- folder/file

copy file to a file (create a folder)

 # before
 ├── --- file

st-cp file folder/new-file

 # after
 ├── --- file
 ├── --- folder/new-file

copy folder to folder

 # before
 ├── --- folder

st-cp folder folder1

 # after
 ├── --- folder
 ├── --- folder1

copy files and folders to destination

 # before
 ├── --- file1
 ├── --- file2
 ├── --- folder1
 ├── --- folder2

st-cp file folder dist

 # after
 ├── --- file1
 ├── --- file2
 ├── --- folder1
 ├── --- folder2
 ├── --- dist/file1
 ├── --- dist/file2
 ├── --- dist/folder1
 ├── --- dist/folder2

Exceptional:

copy file to existing folder

 # before
 ├── --- file
 ├── --- folder

st-cp file folder

 # after
 ├── --- file
 ├── --- folder
 ├── --- folder/file

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

feat: add hat wobble
^--^  ^------------^
|     |
|     +-> Summary in present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.

More Examples:

  • feat: (new feature for the user, not a new feature for build script)
  • fix: (bug fix for the user, not a fix to a build script)
  • docs: (changes to the documentation)
  • style: (formatting, missing semi colons, etc; no production code change)
  • refactor: (refactoring production code, eg. renaming a variable)
  • test: (adding missing tests, refactoring tests; no production code change)
  • chore: (updating grunt tasks etc; no production code change)

References:

  • https://www.conventionalcommits.org/
  • https://seesparkbox.com/foundry/semantic_commit_messages
  • http://karma-runner.github.io/1.0/dev/git-commit-msg.html

Thank you so much for supporting us financially! 🙏🏻😎🥳👍

SpringType is brought to you by:

Please help out to make this project even better and see your name added to the list of our CONTRIBUTORS.md :tada: