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

path-run

v0.1.0

Published

esay change you require paths Now

Downloads

4

Readme

path-runBuild Status codecov explain

Esay change you require paths now

Chinese|English

If you change the location of a file, then the corresponding file modification of other files is a problem.

You can trypath-run, change your file location is not so manual

Install

npm install --global path-run

Correct use of -cli

  1. Copy files to destination

    • demo

      • index.js
      • input
        • input1.js
        • input2.js
      • output
        • output1.js
        • output2.js
    • demo

      • index.js
      • input
        • ✂️input1.js // <===== copy to output
        • input2.js
      • output
        • ➕output3.js // <===== from input/input1.js
        • output1.js
        • output2.js
  2. RunningCli

path-run demo/input/input1.js demo/output/output3.js
# path-run [input] [output]

1⃣️Process.cwd()All references belowInputThe path will becomeOutput 2⃣️ Output file , inside require/import file path change right relative path

  1. RemoveInput1.js

    • demo
      • index.js
      • input <===== ✂️cut
        • input2.js
      • output
        • output3.js // <===== from input/input1.js
        • output1.js
        • output2.js

real-project transltemds

cli demo

demo-cli-show

inpath with outpath diff

inpath-diff-outpath

other require file diff

index-diff


Warnning⚠️ , path-run do not change package.json main or bin string, pleace rechange yourself


Api

Pathrun({options})

Options

1. InPath

Type:String

Abs path

2. OutPath

Type:String

Abs path

3. cwd

Type:String

Default :Process.cwd()

return

Type: Array

Array[i] like this

const options = {
  files: 'path/to/file',
  from: /foo/g,
  to: 'bar',
};

by replace-in-file use

https://github.com/adamreisnz/replace-in-file

Cli

npm install --global path-run

  esay change you require paths Now

  Usage
    $ path-run [input] [output]

  Options
        input  「want to change」
        output  [turn on ]

  Examples
        $ path-run './index' './lib/index'

  will change all process.cwd()/* files require Path 'index' => './lib/index'

concat

nodepaths js module map

License

Mit ©Chinanf-boy