Skip to content

A couple suggestions #21

@AndreaPontrandolfo

Description

@AndreaPontrandolfo

First off, thank you for this library! It's so good!

I tried eslint-plugin-paths a few months ago, but it never worked for me. Nothing at all.
I tried to give feedback, but apparently the author abandoned the project right after publishing the repo.

I just found this project, tried it, and it worked flawlessly at whatever I threw at it!

I have some feedback.

  1. Here i think you should reword it as: "Enforce the use of defined aliases". As "enforce" is a more frequently used word than "encourage" in the ESLint ecosystem
  2. The plugin already work for with the ESLint Flat Config, but you should document this explictely in the README
  3. Consider extending the scope of the plugin to Nodejs sub-import paths
  4. Here you probably shouldn't base anything of your library off Typescript baseUrl. See why

Regardless, i'll start to use this immediately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions