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

parcel-resolver-project-root

v2.1.3

Published

Resolve your imports from './src' and not have to use a tilde or other alias.

Downloads

5

Readme

parcel-resolver-project-root

Build Status

Resolve your imports from './src' and not have to use a tilde or other alias.

Installation

With npm:

$ npm install --save-dev parcel-resolver-project-root

With yarn:

$ yarn add --dev parcel-resolver-project-root

Usage

In the .parcelrc file for your project, add this to the list of resolvers. A blank configuration with nothing but this plugin in it would look like:

{
  "extends": "@parcel/config-default",
  "resolvers": ["parcel-resolver-project-root", "..."]
}

Note that the "..." entry is literal - that tells Parcel to use the rest of its default resolvers there. Without that, your project likely will not build.

Example

After adding that to your parcel config, say you have a project layout like this:

my-awesome-project
├── package.json
├── package-lock.json
├── README.md
└── src
    ├── constants.js
    └── index.js

You can now do this -

import constants from 'constants';

...from anywhere in your project and trust that it will resolve correctly.

Why?

I really liked being able to do this with NextJS and SWC/babel, and Parcel seemed to be lacking this feature. Looking at their plugin API, implementing it as a plugin seemed trivial - so I did.

I may add configuration options later to support more filetypes or the like, submit a GitHub issue if there's any features you'd like to see in the project!