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

svdesignti-vault

v1.0.2

Published

Sync your .env file with SvDesignTi Vault.

Downloads

4

Readme

SvDesignTi Vault CLI

The SvDesignTi Vault CLI allows you to connect to your Envault server and sync its credentials to your local .env file.

Usage

To use the SvDesignTi Vault CLI, you must have Node.js installed on your computer.

On your dashboard, you will find an initialization command for each environment, which you can run to establish a connection to your server, and pull your variables. This command only needs to be run the first time you connect your .env. An example initialization command:

npx envault vault.envault.dev 84632 iCNaGGLou6v0mRas

After you've run your environment initialization command for the first time, you can pull your .env again easily:

npx envault

Options

By default, Envault will not pull variables that are not already present in your .env file. To enable this behaviour, use the --constructive flag:

npx envault --constructive

You are able to customise the name of your .env file using the --filename flag:

npx envault vault.envault.dev 84632 iCNaGGLou6v0mRas --filename=.myenv

The Envault CLI will sometimes prompt you to confirm your actions, especially those made in constructive mode. To bypass these prompts, use the --force flag:

npx envault --force

Handling multiple environments

You can store multiple environments instead of overwriting when authenticating a new environment.

You are able to sync a specific .env by providing the server and environment ID. This is especially useful if you have multiple .env files. For example:

npx envault envault.server.test 1 llT8J6tEDbtJgSln 
npx envault envault.server.test 2 BXYtZdNkQjtWSqE6

Now, you may sync each environment:

npx envault 												// Will still sync .env from "1"
npx envault envault.server.test 2 --filename=.env.settings  // Will sync .env.settings from "2"

If no server and environment provided it will default to the first environment that was added.

Need Help?

🐞 If you spot a bug with Envault, please submit a detailed issue, and wait for assistance.

🤔 If you have a question or feature request, please start a new discussion.

🔐 If you discover a vulnerability within Envault, please review our security policy.