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-plugin-import-no-duplicates-prefix-resolved-path

v2.0.0

Published

A replacement for the [`eslint-plugin-import/no-duplicates`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-duplicates.md) rule that includes an option to take into account the imported module name when considering duplicates.

Downloads

1,095

Readme

eslint-plugin-import-no-duplicates-prefix-resolved-path

A replacement for the eslint-plugin-import/no-duplicates rule that includes an option to take into account the imported module name when considering duplicates.

Usage

Include this plugin in your eslint config:

{
  // ...other config
  plugins: [
    // ...other plugins
    'import-no-duplicates-prefix-resolved-path'
  ],
  // ...other config
}

Disable the eslint-plugin-import/no-duplicates rule and enable this one:

{
  // ...other config
	rules: {
    // ...other rules
		'import/no-duplicates': 0,
		'import-no-duplicates-prefix-resolved-path/no-duplicates': [
			'error',
			{
				prefixResolvedPathWithImportName: true,
			},
		],
    // ...other rules
	},
  // ...other config
}

Configure

The options for this rule are the same as eslint-plugin-import/no-duplicates with the added prefixResolvedPathWithImportName option.

Default options:

{
  considerQueryString: false,
  'prefer-inline': false,
  prefixResolvedPathWithImportName: false // must be set to true to enable
}

Background

The eslint-plugin-import/no-duplicates rule is a problem for projects that import modules from libraries that declare multiple modules in a single typescript declaration file. For example @sveltejs/kit declares several $app/ modules in a single ambient.d.ts file.

This results in a duplicate import error when importing from multiple $app/ modules. For example:

import { page, getStores } from '$app/stores';
import { goto } from '$app/navigation';

Results in the error:

1:34  error  '/path/to/project/node_modules/@sveltejs/kit/types/ambient.d.ts' imported multiple times  import/no-duplicates
2:23  error  '/path/to/project/node_modules/@sveltejs/kit/types/ambient.d.ts' imported multiple times  import/no-duplicates

This modified rule includes the module name in the resolved import path to differentiate between modules that resolve to the same file.

In this case the resolved path for both imports would instead be:

$app/stores:/path/to/project/node_modules/@sveltejs/kit/types/ambient.d.ts

and

$app/navigation:/path/to/project/node_modules/@sveltejs/kit/types/ambient.d.ts

This removes the duplicate import error and still allows for auto fixes when there are actual duplicates.

For example:

import { page } from '$app/stores';
import { getStores } from '$app/stores';
import { goto } from '$app/navigation';

Will still be auto fixed to:

import { page, getStores } from '$app/stores';
import { goto } from '$app/navigation';

There are a lot of possible solutions for this issue, this is just one of them. Follow the issue on the repo here.