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

symlink-to

v0.0.4

Published

Get to npm project root folder via a symlink created on install.

Downloads

7

Readme

Symlink To NPM Project Root

import Bar from 'symlink-to/project-root/foo/bar';
// or
const Bar = require('symlink-to/project-root/foo/bar');

I Don't Know

  1. If you import the same module by different paths will webpack optimize it?
  2. May NPM put this package to a folder different than ./node_modules/symlink-to (for shared module optimization, e.g.) and thus break symlinks to ./../..?

node_modules Compatability

Symlinks generated on Windows won't be compatible with Linux and vice versa. Only junctions created in Windows are portable. You will have to reinstall symlink-to package or invoke npm run install inside its folder if you want to reuse node_modules on other OS.

If you know any other ways to quickly convert symlinks of node_modules recursively —, please, let me know.

Symlinks Compatability Table

Type | Linux | Windows | WSL --------------------------|------------------------|-------------------------|------------------------ WSL symlink | no | no | yes mklink /J (junction) | Works as absolute link | Works as absolute link | Works as absolute link mklink /D (dir, symbolic) | no | yes | no mklink /H (hard) | - | Can't link to directory | - Linux symlink | yes | no | no

WSL is Windows Subsystem for Linux (bash for Windows).