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

eslint-import-resolver-parcel

v1.10.6

Published

Parcel import resolution plugin for eslint-plugin-import.

Downloads

1,456

Readme

eslint-import-resolver-parcel

Build Status Known Vulnerabilities

About

Parcel import resolution plugin for eslint-plugin-import. This allows for eslint/import to work with parcel's module resolution.

Installation

npm install eslint-import-resolver-parcel -D

Usage

Add this to your eslint config:

settings: {
  'import/resolver': 'parcel'
}

Current status

  • [x] Relative paths (import foo from '../foo.js')
  • [x] Absolute paths (import _ from 'lodash')
  • [x] Tilde paths (import foo from '~/foo.js')
  • [x] Root paths* (import foo from '/foo.js')
  • [x] Aliasing (parcel docs)
  • [ ] Glob Paths (parcel docs)

*About Root Paths

Because root paths require knowledge of the entry points, you must pass in the folder where the entry points are located into the config:

settings: {
  'import/resolver': {
    parcel: {
      rootDir: 'src' // wherever your entrypoints are located
    }
  }
}

If not specified, it will assume process.cwd() (where eslint is called from, probably where the package.json is located).

Extensions

If you want to automatically add extra extensions to resolve to, e.g., test-file resolves to test-file.ts, just pass in an array to the extensions key of the config.

settings: {
  'import/resolver': {
    parcel: {
      extensions: ['.ts'] // whatever extra extensions you want to look for
    }
  }
}

Current default extensions are .js and .jsx.