Catalog npm
Back to packageRELEASE DETAILS

1.0.6

npm

4snap

#### Discover, Share, & Execute Commands Anytime Anywhere

Published28 Jun 2023
Direct dependencies19
Transitive dependenciesNot calculated

README

Current package documentation

4snap

Discover, Share, & Execute Commands Anytime Anywhere

4snap image

Overview

4SNAP is a command snippet manager designed to simplify and streamline your development workflow. It allows you to save and organize your frequently used command snippets, making it easy to retrieve and execute them whenever needed. With 4SNAP, you can increase your productivity, reduce repetitive typing, and improve code consistency.

Table of Contents

Getting Started

  • Account Creation
  • Install 4Snap CLI
  • Authenticate 4Snap CLI
  • Create Commands
  • Executing Commands
  • Synchronization
  • View Saved Commands
  • Sharing Command

Getting Started

Follow the steps below to get started with 4Snap.

1. Account Creation

Get started by creating an account on 4Snap using this LINK. This will allow you to access and manage your commands.

2. Install 4Snap CLI

After creating an account on 4Snap, you need to install the 4Snap CLI npm package. Use the following command to install it:

# npm users
$ npm install 4snap

# yarn users
$ yarn add 4snap

3. Authenticate 4Snap CLI

Before you can execute any command, you need to authenticate the 4Snap CLI. Use the following command to authenticate:

$ 4snap login

This command will prompt you for a 4Snap token, which can be obtained from your settings page on 4Snap if you are currently logged in.

4. Create Commands

You can create commands or collections of commands either using the web interface or the CLI. To create a command using the CLI, run the following command:

$ 4snap create

This command will guide you through the steps needed to create your favorite command or collections of commands. Collections of commands are created by separating them with a comma (,).

5. Executing Commands

You can execute both local and public commands using the 4Snap CLI. To execute a local command, use the following command:

$ 4snap run [COMMAND_NAME]

For executing a public command, use the following command:

$ 4snap run -p [COMMAND_NAME]

Replace [COMMAND_NAME] with the name of the command you want to execute.

6. Synchronization

Sometimes, the commands created via the web interface may not be available on your local machine. To synchronize all created collections of commands and make them available on your local machine, use the following command:

$ 4snap sync

This command will ensure that all your created commands are synchronized.

7. View Saved Commands

To view your saved commands or collections of commands locally, use the following command:

$ 4snap list

This command will print out all available saved commands in a table format on your terminal.

8. Sharing Command

If you want to share your saved commands with others, whether publicly or privately, you can do so using the following command:

$ 4snap share -u [USER_NAME] [COMMAND_NAME]

Replace [USER_NAME] with the recipient's username and [COMMAND_NAME] with the name of the command you want to share.

Examples

  1. 👷🏻 Command meant to ease the process at which developers start a new project. for eg mkdir project_name, cd project_name, touch file_name can be shorten into 4snap run setup.

Here are lists of commands you could try out with 4snap.

  1. mkdir $project_name,cd $project_name,touch $file_name
  2. npm list -g
  3. yarn create vite $appName --template $templateName

Downloads & popularity

Awaiting observations

No metric observations yet

Download counts and popularity will appear here as the collector receives them.

Declared dependencies 19

Native requirements
19 direct targetsNot calculated transitive count
Package / targetRequirementRelationship
@clack/prompts
Environment
{
  "local_name": "@clack/prompts",
  "alias": false,
  "peer_metadata": null
}
^0.6.3runtime
axios
Environment
{
  "local_name": "axios",
  "alias": false,
  "peer_metadata": null
}
^1.4.0runtime
chalk
Environment
{
  "local_name": "chalk",
  "alias": false,
  "peer_metadata": null
}
^5.2.0runtime
cli-table
Environment
{
  "local_name": "cli-table",
  "alias": false,
  "peer_metadata": null
}
^0.3.11runtime
commander
Environment
{
  "local_name": "commander",
  "alias": false,
  "peer_metadata": null
}
^11.0.0runtime
conf
Environment
{
  "local_name": "conf",
  "alias": false,
  "peer_metadata": null
}
^11.0.1runtime
cross-spawn
Environment
{
  "local_name": "cross-spawn",
  "alias": false,
  "peer_metadata": null
}
^7.0.3runtime
dotenv
Environment
{
  "local_name": "dotenv",
  "alias": false,
  "peer_metadata": null
}
^16.3.1runtime
execa
Environment
{
  "local_name": "execa",
  "alias": false,
  "peer_metadata": null
}
^7.1.1runtime
fs-extra
Environment
{
  "local_name": "fs-extra",
  "alias": false,
  "peer_metadata": null
}
^11.1.1runtime
inquirer
Environment
{
  "local_name": "inquirer",
  "alias": false,
  "peer_metadata": null
}
^9.2.7runtime
ora
Environment
{
  "local_name": "ora",
  "alias": false,
  "peer_metadata": null
}
^6.3.1runtime
shelljs
Environment
{
  "local_name": "shelljs",
  "alias": false,
  "peer_metadata": null
}
^0.8.5runtime
slugify
Environment
{
  "local_name": "slugify",
  "alias": false,
  "peer_metadata": null
}
^1.6.6runtime
@types/axios
Environment
{
  "local_name": "@types/axios",
  "alias": false,
  "peer_metadata": null
}
^0.14.0development
@types/inquirer
Environment
{
  "local_name": "@types/inquirer",
  "alias": false,
  "peer_metadata": null
}
^9.0.3development
@types/node
Environment
{
  "local_name": "@types/node",
  "alias": false,
  "peer_metadata": null
}
^20.3.1development
@types/shelljs
Environment
{
  "local_name": "@types/shelljs",
  "alias": false,
  "peer_metadata": null
}
^0.8.12development
typescript
Environment
{
  "local_name": "typescript",
  "alias": false,
  "peer_metadata": null
}
^5.1.3development

Distribution files

1 collected
Distribution 1

Source distribution

Source file
Checksums from source
{
  "integrity": "sha512-KagnBQrl6A3jNstoidl4/csYS++Ss78ytzM7xSnYrXVJyJMQd8srP531oWBaWR6NMIpL3pnFdVn1FckHtpa9Ew==",
  "shasum": "0b5dab0b9b40efb15a853b83e602e77f568a6e4a",
  "tarball": "https://registry.npmjs.org/4snap/-/4snap-1.0.6.tgz",
  "fileCount": 42,
  "unpackedSize": 55869,
  "signatures": [
    {
      "keyid": "SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA",
      "sig": "MEYCIQDb2BJODlj23zYprEtoJCo6flohBqQAiKumBKpaB803dwIhALnJegmHu34S/yA17wYf9ER/UlX/CoRIb0dpvx+vXqKg"
    }
  ]
}

Metadata history

Meaningful changes
Current collected state Current

Observed since 20 Oct, 20:18 UTC

No superseded metadata states collected. Unchanged observations do not create new revisions.

Record identity

package_version:0d1ecaef0c8e045ad237ff6aedf7dab07b742b7e9ee706f398a616f9ffd2e29e

Other collected versions

1.1.028 Jun1.0.928 Jun1.0.828 Jun1.0.728 Jun1.0.528 Jun1.0.427 JunView all collected versions →