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

bbedit-recovery

v0.0.2

Published

NPM package that helps get settings from BBEdit

Downloads

13

Readme

BBEdit Recovery

Code Climate maintainability Code Climate issues Github code size GitHub issues GitHub last commit GitHub License GitHub forks GitHub stars

So over the last few years as a developer I've experienced three instances of MacBook swollen battery syndrome. I do not know if I'm just scripting too much, too many projects with npx calls for React :zany_face: , or just bad luck. Either way I've found over time I was manually copying over my BBEdit settings to my NAS so I could easily setup my replacement/loaner and in the process thought there has got to be a better way then manual and could this help anyone else :thinking: .

To resolve this headache and since I've enjoyed writing more in Node I thought it be fun to write a Node CLI. Currently this is very basic but in my free time (if ever :roll_eyes: ) I'm thinking of building in launchd support that pushes to a repository and/or NAS.

Installation

NPM:

npm i bbedit-recovery

install dependencies

cd bbedit-recovery && npm i

NPM link

After dependencies are added run:

npm link

If you're done run to remove

npm unlink

How to use

This package can take three CLI commands:

bbedit-recovery
bbedit-recover

or the shorthand:

bbrec

by default with no options passed this will create a directory named bbedit-recovery and copy over all directories that are not empty and files. This location can be echoed with the pwd command in the terminal if you're unsure where files will go.

Options

What's a CLI without options, right? Currently this takes two dest and name but I can assure you there will be more in the future.

Destination

You can specify where the files will be copied to by passing either the commands --name or the shorthand -n. This expects and tests for a directory. If a directory isn't valid it will error out.

Example:

bbedit-recover -dest /Users/$USER/supercalifragilisticexpialidocious

shorthand:

bbrec -d /Users/$USER/supercalifragilisticexpialidocious

Desktop and Documents

If you'd like to copy files to your Desktop directory:

bbedit-recover -d Desktop

If you'd like to copy files to your Documents directory:

bbedit-recover -dest Documents

ewww.. a shorthand for Documents:

bbedit-recover -d Docs

Name

Well, I'm hurt that you do not like the name bbedit-recovery. Fine, so be it, there is an option to change it just for you:

bbedit-recover -dest /Users/$USER/Desktop/supercalifragilisticexpialidocious -name recovery

shorthand:

bbrec -d /Users/$USER/Desktop/supercalifragilisticexpialidocious -n recover

Intro

What's a CLI without a groovy terminal banner:

bbedit-recovery intro

Help

Documentation writing is soooo boring. If I add a feature and forget to update the README.md you can get a listing of the commands:

bbedit-recovery --help

Future Plans

  • [ ] Add exclusion parameters
  • [ ] Run off a launchd
  • [ ] Ability to push to a repo