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

renova

v0.1.0

Published

Patches unqualified exports and imports in installed packages by appending the appropriate file names and extensions.

Downloads

2

Readme

Overview

renova patches third-party packages with non-fully-ESM-compliant source and/or TypeScript declaration files (e.g. @apollo/client) by appending explicit file names and extensions to unqualified export and import statements, facilitating nodenext/node16+ module resolution of dependencies with legacy exports.

For example, given the following source tree:

  • directory/
    • index.js
  • file.js

Unqualified exports and imports are corrected as follows:

Input

export {foo} from './directory';
import bar from './file';

Output

export {foo} from './directory/index.js';
import bar from './file.js';

Usage

Automatic

📍 package.json

{
  "scripts": {
    "dependencies": "renova @apollo/client"
  }
}

This will patch @apollo/client's .d.ts files whenever dependencies are installed or upgraded.

💡 Note that, when run from the dependencies lifecycle script, no output may be printed. In contrast, postinstall does allow output but is only executed when installing all dependencies; not when installing or upgrading one or more specific packages.

Manual

$ npx renova [--dry-run] [--extensions=<extension>,...] [--verbose] <package> ...

    <package>: Name of a package under ./node_modules to patch, e.g. '@apollo/client'.

    --dry-run: Print potential outcome without altering files. Implies --verbose.
 --extensions: Comma-separated list of file name extensions to process. Defaults to '.d.ts'.
    --verbose: Print all matching exports and imports.

Example

# first-time run
$ npx renova --verbose @apollo/client
./node_modules/@apollo/client/cache/core/cache.d.ts
         🛠️ ../../utilities → ../../utilities/index.js
         🛠️ ./types/DataProxy → ./types/DataProxy.js
         🛠️ ./types/Cache → ./types/Cache.js
...

# safe to run on an already-patched package
$ npx renova --verbose @apollo/client
./node_modules/@apollo/client/cache/core/cache.d.ts
         ✔️ ../../utilities/index.js
         ✔️ ./types/DataProxy.js
         ✔️ ./types/Cache.js
...