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

vscode-variables

v1.0.1

Published

Replace VSCode predefined variables for extensions

Downloads

2,544

Readme

VSCode Predefined Variable Parser

Predefined variables The following predefined variables are supported:

${homeDir} - the home directory of the user
${workspaceFolder} - the path of the folder opened in VS Code
${workspaceFolder:name} - the path of the folder opened in VS Code with the name
${workspaceFolderBasename} - the name of the folder opened in VS Code without any slashes (/)
${workspaceFolderBasename:name} - the name of the folder opened in VS Code without any slashes (/) with the name
${file} - the current opened file
${fileWorkspaceFolder} - the current opened file's workspace folder
${relativeFile} - the current opened file relative to workspaceFolder
${relativeFileDirname} - the current opened file's dirname relative to workspaceFolder
${fileBasename} - the current opened file's
${fileBasenameNoExtension} - the current opened file's basename with no file extension
${fileDirname} - the current opened file's dirname
${fileExtname} - the current opened file's extension
${cwd} - the task runner's current working directory on startup
${lineNumber} - the current selected line number in the active file
${selectedText} - the current selected text in the active file
${pathSeparator} - the character used by the operating system to separate components in file paths
${/} - short for ${pathSeparator}
${env:<variable>} - return the env variable
${config:<variable>} - return the settings configuration
${command:<command>} - execute a command and return the result

Install the package:

npm i -S vscode-variables

Using the package

Once

const vscodeVariables = require('vscode-variables');

vscodeVariables('${file}'); //will return the fsPath of the file.

Recursive

const vscodeVariables = require('vscode-variables');

vscodeVariables('${file}',true); //will return the fsPath of the file.