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

customcode

v0.3.0

Published

A way to use a custom VS Code for each project.

Downloads

6

Readme

Custom Code

Build
status Build status npm

A tool to help run a custom VS Code for each project. This allows you to have different user settings and different extensions for each instance.

So, for example, if you are working on an Angular project you use only Angular extensions, and if you later work on a React project, you use React extensions.

Multiplatform. Tested on Windows and Linux. Node.js based.

This allows you to have different extensions and preferences for each version.

This is only tested on Node.js 8 and 10. We cannot guarantee it on other Node.js versions.

Installing

npm install -g customcode

Or grab the source and

npm install -g

Using

Simply run ccode on any directory and it will search for the custom VS Code and launch it:

ccode .

You should use ccode as you always used code. If a custom code is found than it will be launched, otherwise your system code will launch.

To create a custom code (preview) run:

create-custom-code <destination-directory>

This will create a .code directory on the specified directory.

How this tool works

We search for code/ccode (or code\ccode.cmd for Windows) from the current working directory (cwd) all the way up to the root directory (/ or usually c:\ on Windows). This is your custom VS Code, with your custom options and extensions.

If a custom VS Code is not found we will search your PATH environment variable for code (or code.cmd on Windows) and use that.

We will then launch VS Code forwarding any command line options you passed originally.

For example, supose your cwd is /home/user/projects/foo/bar/ and you type on your terminal:

~/projects/foo/bar $ ccode .

We will search for:

/home/user/projects/foo/bar/.code/ccode
/home/user/projects/foo/.code/ccode
/home/user/projects/.code/ccode
/home/user/.code/ccode
/home/.code/ccode
/.code/ccode

Let's say /home/user/projects/foo/.code/ccode is found, we will then launch:

/home/user/projects/foo/.code/ccode .

Using /home/user/projects/foo/bar/ as the current working directory.

Creating a custom VS Code instalation

A custom VS Code simply sets the user data dir and the extensions dir to a different location. This is what this tool does. It creates the code (code.cmd for Windows) and its subdirectories.

To use it simply type create-custom-code <directory> to create a custom code in that directory. The destination directory (<directory> above) will receive a new code directory and a ccode (or ccode.cmd) with the correct configuration. Extensions will be installed on .code/extensionsdir and settings and other configurations will go on .code/userdatadir.

This custom code installation will work seamlessly with the ccode tool.

Troubleshooting

If your custom VS Code is not running then check your ccode (or ccode.cmd) script. We are not responsible for it.

If you find any problems, open an issue on Github with the steps to reproduce your problem.

Contributing

Questions, comments, bug reports, and pull requests are all welcome. Submit them at the project on GitHub.

Bug reports that include steps-to-reproduce (including code) are the best. Even better, make them in the form of pull requests.

Author

Giovanni Bassi

License

Licensed under the Apache License, Version 2.0.

License

This software is open source, licensed under the Apache License, Version 2.0. See LICENSE.txt for details. Check out the terms of the license before you contribute, fork, copy or do anything with the code. If you decide to contribute you agree to grant copyright of all your contribution to this project, and agree to mention clearly if do not agree to these terms. Your work will be licensed with the project at Apache V2, along the rest of the code.