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

vmf-tools

v1.0.1

Published

Various programmatic modifiers for VMF files

Downloads

16

Readme

VMF Tools

Programmatically modify VMF files.

Rules

Currently the following is implemented:

Usage

The tool can be ran in two ways: manually, or as part of the compile step. In both cases you must install Node.js, as this is what is used to actually execute the toolset.

As part of compilation

This is the most user friendly way once you've set it up, as it works more or less transparently.

  1. Download vmf-tools.exe
  2. Go to your Hammer compilation settings (F9) and enable advanced mode if not already set.
  3. For each mode you want to compile in, do the following:
    1. [Optional] Copy the configuration configuration
    2. Add a new command, pick the vmf-tools.exe as executable
    3. Enter $path\$file.$ext $path\$file-processed.$ext as parameters
    4. Make sure the new command is the top-most command and is enabled
    5. In all other commands, replace $path\$file with $path\$file-processed

Done. Whenever you compile the map it will now automatically be processed.

Manually

Run the tool manually, specifying the VMF as the first argument and the output as the second argument (npx vmf-tools path\to\map.vmf path\to\processed.vmf).

Configuration

The configuration usually happens through Hammer by using custom keyvalues. The specifics of how this works can be found on each rule's README.

For more advanced configuration a configuration file is needed. This is simple a .js file that contains module.exports = { rules: { /* config goes here */ } }, with the configuration as specified in each rule's README.

If you want to use a configuration file you must tell the tool about it. This is done by going to Map > Map properties... in Hammer and adding a keyvalue of vmft_config with the value being the path to the config file. You may also give the path to the file as the third argument if you run the tool manually.

If the configuration file is specified as a map property and as the third argument when running the tool, then the one specified as a map property will be used.