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

vendorism

v3.0.0

Published

This library provides utilities for managing vendor files, hooks, and dependencies.

Downloads

286

Readme

Vendorism

This library provides utilities for managing vendor files, hooks, and dependencies.

Functions

get

This function is responsible for setting up the source based on a given configuration.

Parameters:

  • config: The configuration object.
    • get: The source configuration.
      • url (optional): The URL from which files should be downloaded.
      • path: The directory to which files should be extracted.
      • hooks (optional): Hooks to run before and after the main process.
        • before (optional): A command to run before the main process.
        • after (optional): A command to run after the main process.

Usage:

await get({
	get: {
		url: "https://example.com/source.zip",
		path: "./path/to/extract",
		hooks: {
			before: "echo Setting up source...",
			after: "echo Source setup complete.",
		},
	},
});

set

This function sets up the target based on the provided configuration.

Parameters:

  • config: The configuration object.
    • set: The target configuration.
      • path: The path for the target.
      • head (optional): The header content to prepend to target files. Uses a default if not provided.
      • hooks (optional): Hooks to be executed before and after target processing.
        • before (optional): Command to be executed before target processing.
        • after (optional): Command to be executed after target processing.
      • transforms (optional): An array of transform functions that can modify content and file paths. Each transform function takes the current file path and content as parameters and returns an object with potentially modified path and content.

Usage:

await set({
	set: {
		path: "./path/to/target",
		head: "/* Custom Header */",
		hooks: {
			before: "echo Setting up target...",
			after: "echo Target setup complete.",
		},
		transforms: [
			(path, content) => {
				return {
					path: path.replaceAll(
						"dependency.js",
						"transformed-dependency.js"
					),
					content: content.replaceAll(
						"./dependency",
						"./transformed-dependency"
					),
				};
			},
		],
	},
});

Examples:

Transforming Content

Using transforms, you can modify file content:

const localConfig = {
	set: {
		// ... other config options
		transforms: [
			(path, content) => {
				return { path, content: content.replace("Hello", "Goodbye") };
			},
			(path, content) => {
				return { path, content: content.replace("World", "Someone") };
			},
		],
	},
};

Transforming File Paths

Similarly, you can also modify file paths:

const localConfig = {
	set: {
		// ... other config options
		transforms: [
			(path, content) => {
				return {
					path: path.replaceAll(
						"dependency.js",
						"transformed-dependency.js"
					),
					content: content.replaceAll(
						"./dependency",
						"./transformed-dependency"
					),
				};
			},
		],
	},
};

eject

This function allows you to eject a file from being managed by the system. Ejecting involves removing a specific header from a file.

Parameters:

  • file: The path to the file that should be ejected.
  • config (optional): The configuration object.
    • set: The target configuration.
      • head (optional): The header content that should be removed from the target file. Uses a default if not provided.

Usage:

await eject("./path/to/target/file.js", {
	set: {
		head: "/* Custom Header */",
	},
});

This will remove the custom header (or the default header if not provided) from the specified file.