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

dtfls

v1.1.0

Published

Back up and restore your config files.

Downloads

8

Readme

dtfls

npm

Back up and restore your config files.

This is a port of dotfiles to Node.js.

Requirements

  • Node v6.0.0 or higher

Install

via npm:

npm install -g dtfls

Usage

CLI

  • Print difference between local and system configs

      dtfls diff <APP...>
  • Install local configs to the system

      dtfls install <APP...>
  • Print system installation path

      dtfls path <APP>
  • Run post-install scripts (it is being run automatically after install)

      dtfls postinstall <APP...>
  • Pull configs from the system to the local folder

      dtfls pull <APP...>

Use dtfls --help to read a common usage information and dtfls <command> --help to read about a specific command.

Folder structure

Each set of configs should be placed in separate folders. Names of such folders should not contain spaces. These folders should contain the same hierarchy which should be in the user folder (~) of the target system.

Mapping of local path to system path for particular configs can be changed with a file path.user.json.

Additionally there is a support for post-install scripts. They can be added in postinstall.user file.

Example

Local repo structure:

my configs
  \_ git
  |  \_ .gitconfig
  |
  |_ profile
  |  \_ .profile
  |
  |_ sublime-text-3
  |  \_ .config
  |     \_ sublime-text-3
  |        \_ Packages
  |           \_ User
  |              |_ Default (Linux).sublime-keymap
  |              |_ Default (Linux).sublime-mousemap
  |              \_ Preferences.sublime-settings
  |
  |_ zsh
  |  \_ .zshrc
  |
  |_ path.user.json
  \_ postinstall.user.js

And a workflow example:

$ cd "my configs"
$ git pull                          <--- pull changes from your repo with configs
$ dtfls install git                 <--- install git configs from the repo to system
$ dtfls pull sublime-text-3         <--- copy Sublime Text configs from system to the local repo
$ git commit -am "Update Sublime Text configs"    <--- commit updated configs
$ git push                                        <--- and push