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

bau-analyser

v1.0.6

Published

CLI to refactor (move) typescript files correcting imports

Downloads

2

Readme

bau-refactor

CLI to refactor (move) typescript files correcting imports

This is a work in progress (now has automated tests - not 100% - and applies inversion of control).

So far, it works like:

  1. Go to a project root (dir containing tsconfig.json)
  2. Suppose you want to move src/classA.ts to src/somePackage/classA.ts.
  3. You say: bau-move ./src/classA.ts ./src/somePackage/classA.ts
  4. The file gets moved, all its relative imports are updated in the moved file (so nothing breaks) and all files that imported yours using relative paths are also updated (all involved files should have been saved beforehand)

Some details:

  1. Save your source files before attempting to move one of them !
  2. Only .ts, .d.ts and .tsx files can be moved
  3. Should work for both Windows and UNIX. So, bau-move a\b.ts a\c.ts should work, for example.
  4. CLI commands consider your cwd as a "project root" and will only see source files under this directory.
  5. Should something go wrong while processing the move, nothing will be done and an error message will be displayed (the exception here is if some IO error occurs while import statements are being corrected in source files, case in which the move will fail half-way, with some corrections done and others not)

Caution

No guarantee of properly working at all cases. Does not support rootDirs or paths in tsconfig.json. Only cares about relative imports (those starting with './' or '../')

Changelog

1.0.3

  • Introduces spec for every class but FileMover.
  • Removes global dependency on rimraf (unless for developing the package, which is not the case of someone who only uses its move feature)

1.0.4

  • bau-move command no longer displays horrible stack-traces, only short error message (in case of failure, obviously)