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

common-cache-path

v1.0.0

Published

Finding the best and standard place to store cache. Especially useful for library authors. A smarter and more customizable alternative to find-cache-dir.

Downloads

6

Readme

Common Cache Path

npm version download codecov License CircleCI

Finding the best and standard place to store cache. Especially useful for library authors. A smarter and more customizable alternative to find-cache-dir.

Difference

  • Zero config with smart defaults.
  • Smart resolution of namespace without the need to manually specify via the name option.
  • Default shared cache directory sits in <ProjectRoot>/.cache instead of <ProjectRoot>/node_modules/.cache to support Yarn PnP and avoid modifying node_modules.
  • Cache location can be overridden to other places to enable easier testing and greater flexibility. For example, when using Netlify with webpack loaders and plugins, the data can be written directly into /opt/build/cache/ to enable cross-build caching.

Installation

yarn add common-cache-path

Usage

import fs from 'fs';
import { commonCachePath } from 'common-cache-path';

// Assume that
// 1. process.cwd is /users/abc/project/app
// 2. this file is in /users/abc/project/app/node_modules/@foo/bar/lib/index.js
const resolvePath = commonCachePath();
fs.writefileSync(resolvePath('some/file.txt'), 'content');
// /users/abc/project/app/.cache/@foo/bar/some/file.txt is created with content 'content'

Options

Shared Cache Directory

dirname: string
The name of the shared cache directory (or a path relative to the root directory of the project that uses your library).
Optional. The default value is .cache.

Namespace

namespace: string
The namespace of your cache directory. Your cache directory is a child directory inside a shared cache directory. This helps prevent conflict among multiple cache users.
Optional. By default, its value is resolved by finding the package name in the name field of the closest package.json to the caller script of commonCachePath().
For example, if your library calls commonCachePath in node_modules/@foo/bar/lib/index.js, the name field of node_modules/@foo/bar/package.json is used as default namespace.

To make sure that different libraries do not interfere with each other. You are strongly suggested to leave it as default.

Current Working Directory

cwd: string
The path of directory that project root searching should start from.
Optional. The default value is process.cwd().

Issues and Feedback

Please voice your opinion and report bugs in the issues sections of this GitHub project.

Contributing

You are more than welcome to add more functionalities, improve documentation, fix bugs, and anything you think is needed. The build step is pretty self-explanatory. Please refer to CONTRIBUTING.md for more details.

License

MIT