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

projectman

v2.1.2

Published

Hate opening folders? Select and open your projects in your favourite editor straight from your command line without 'CD'ing into the deeply nested folders.

Downloads

33

Readme

ProjectMan🦸

ProjectMan is a CLI which lets you add projects to favorites using command pm add and open them from anywhere you want using command pm open.

Along with this there are also other commands like pm seteditor, pm remove, cd $(pm getpath) mentioned in documentation below.



Installation

With NodeJS installed in your machine,

npm install -g projectman

Commands

pm is an alias of projectman so you can use pm <command> or projectman <command>

📖 Open Project

Opens project in your code editor (Check out pm seteditor command to set your preferred editor)

Usage :

pm open [projectName]

[projectName] is an optional parameter.

Alias: pm o, pm

➕ Add Project or Template

Add project to favorites

cd /till/the/project
pm add

You can pass --url param to add a URL instead of a directory.

🪄 Create Project

Use added projects as a template to create new project

pm create

Alias: pm c

💫 Set Editor

pm seteditor

Sets default editor to open projects from.

To set a different editor for a specific project,

Flag: --for-project

pm seteditor --for-project

Sets different editor for a specific project. E.g You can use VSCode for other projects and Atom for CoolProject1

If your TextEditor/IDE is not listed, You can select option Other from the list and give your editorCommand. Read editorCommand ref for more information.

🏃🏽 cd to a project without opening.

cd $(pm getpath [projectName])

[projectName] is an optional parameter.

Alias : cd $(pm gp)

(Note: This does not work in Windows cmd, You can use it in Windows Powershell)

❌ Remove Project

pm remove

Removes project from favorites.

➖ Remove editor

pm rmeditor

Shows list of project and removes the project specific editor from the project.

pm rmeditor --all

removes all project specific editors.


⚙️ Settings.json

If you want to sort projects/change name of project/change path, You can type pm edit to open settings.json

Example settings:

{
    "commandToOpen": "code",
    "projects": [
        {
            "name": "Project1",
            "path": "path/to/project1"
        },
        {
            "name": "Project2",
            "path": "path/to/project2",
            "editor": "atom"
        },
        {
            "name": "Project3",
            "path": "path/to/project3"
        }
    ]
}

This will show three projects in pm open and project2 will be opened in Atom and other projects will be opened in Visual Studio Code

Settings Ref:

> commandToOpen :

  • This is your editor's command, this command will be used to open the file in your editor.
  • Default is code which opens in vscode.
  • This is the command that you normally use to open directories in your editor.

| Editor |'commandToOpen' value| |---------------|-----------| | VSCode | code | | Atom | atom | | Sublime | subl | | Vim | vim | | WebStorm | wstorm |

> projects.name :

  • This is the name that will be visible when you type projectman open

> projects.path :

  • This should be the absolute path to your folder.

> projects.editor :

  • This is optional key. In case it doesn't exist it will read value from commandToOpen
  • You can use this to specify separate editor for a particular project.
  • You can set it by adding "editor": "<commandToOpen>" in projects array in settings.json (Example is shown above)

ChangeLogs

v2.0.0 @latest

  • Add pm create command
  • Remove support for binaries

For More Changes read CHANGELOG.md


Rust Port

@hskang9 has made a pretty cool rust port for projectman. You can check it out at: https://github.com/hskang9/projectman-rust


Contributing to ProjectMan

contributions welcome to projectman

I would be extremely happy to have people contribute to ProjectMan. You can read Contribution guidelines in CONTRIBUTING.md


Thank you for showing Interest! Do contribute and star ProjectMan🦸 on GitHub