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

mves

v0.1.1

Published

CLI for moving js assets and updating file paths in project dir

Downloads

4

Readme

mves

Build Status npm version

mv ecmascript

mv anything that can be imported by js and have mves automatically resolve import/require statements. This works for js, jsx, scss, css and supports import, require, url statements.

Installation

npm i -g mves

Usage

# example
mves <input> <output>

Example.

Let's say you have this folder structure, and one.js imports two.js the import statement would look something like import two from '../two/two.js'

.
├── one
│   └── one.js
└── two
    └── two.js

After running

mves one/one.js one.js

Your folder structure now looks like this

.
├── one
├── one.js
└── two
    └── two.js

and that import statement now looks like this import two from './two/two.js'

Todo

  • support import foo from './foo' foo could potentially be foo.js or foo/index.js right now it only supports import foo from './foo.js'

  • better logging for user, right now it prints absolute path of modified file, nicer to print relative to project root or specified scope.

  • support multiple input args just like mv for ex. mv foo bar zed dir will move foo bar and zed into dir