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-midi-plugin-import

v0.0.51

Published

the plugin for fix paths of imports

Downloads

13

Readme

eslint-plugin-midi-plugin-import

the plugin for fix paths of imports

page on GitHub

Installation

You'll first need to install ESLint:

npm i eslint --save-dev

Next, install eslint-plugin-midi-plugin-import:

npm install eslint-plugin-midi-plugin-import --save-dev

Usage

Add midi-plugin-import to the plugins section of your .eslintrc configuration file. You can omit the eslint-plugin- prefix:

{
    "plugins": [
        "midi-plugin-import"
    ]
}

Then configure the rules you want to use under the rules section.

This rule is necessary to check the use of relative paths inside slices in accordance with the FSD methodology. (This rule has a fixer.)

{
    "rules": {
        "midi-plugin-import/path-check": 2
    }
}

This rule is necessary to control the production of absolute imports from the public API only. (This rule has a fixer.)

{
    "rules": {
        "midi-plugin-import/public-api-imports": 2
    }
}

This rule is necessary to control the production of imports from the underlying layers. (This rule doesn't have a fixer.)

{
    "rules": {
        "midi-plugin-import/layer-imports": 2
    }
}

If you use an absolute path alias, you need to include the "aliasAbsolutePath" parameter and the alias name.

{
    "rules": {
        "midi-plugin-import/{rule-name}": [2, {"aliasAbsolutePath": "@"}]
    }
}

Rules

🔧 Automatically fixable by the --fix CLI option.

| Name               | Description | 🔧 | | :----------------------------------------------------- | :------------------------------------------------------------- | :- | | layer-imports | restriction on importing overlying layers into underlying ones | | | path-check | checking correct path for feature sliced design | 🔧 | | public-api-imports | The rule prohibits the use of components not from public API | 🔧 |