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

babel-plugin-transform-package-self-reference

v0.1.4

Published

Transfroms package self-references by reading package.json

Downloads

21

Readme

babel-plugin-transform-package-self-reference

Transforms package self-references in commonjs and es modules by changing the self-reference to a path relative to the importing file. Reads the closest package.json to get the package name and the path in the package to resolve the self reference to. If it is a transforming a require will resolve to the file specified in main. When transforming an import it will resolve to the file specified in exports['.'], or module if that is not found.

If you wish to short circuit the above logic and resolve to a custom path, specify a resolveTo path in the plugin's options object.

Examples

// package.json
{
  name: 'my-package',
  main: 'index.cjs',
  exports: {
    ".": 'index.mjs'
  },
}
// folder/file.js
import { foo } from "my-package";
const foo = require("my-package");

// ↓ ↓ ↓

import { foo } from "../index.mjs";
const foo = require("../index.cjs");