Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issue with alias resolver

See original GitHub issue

I am trying to use aliases, usually it works with the https://www.npmjs.com/package/eslint-import-resolver-alias

But when I run the app, the plugin is trowing all the time:

Unable to resolve path to module '@/components/....'

It seems that adding

  "settings": {
    "import/resolver": {
      "alias": {
        "map": [
          ["@", "./src"]
        ]
      }
    }
  },

Is not detected by the vite plugin

Issue Analytics

State:
Created 2 years ago
Comments:7

Top GitHub Comments

1reaction

jakubkojecommented, Aug 26, 2021

You are a legend! Your eslint config pointed me in the right direction and now my vue project works with airbnb config. Thank you very much for your help.

1reaction

a-tonchevcommented, Aug 26, 2021

Here is my eslint:

https://github.com/a-tonchev/react-boilerplate/blob/master/.eslintrc.json

You can check also my package.json for the plugins I am using:

https://github.com/a-tonchev/react-boilerplate/blob/master/package.json

I hope that will help you

Top Results From Across the Web

Support eslint-import-resolver-alias Config · Issue #249

Request to support module aliases as provided by the config in eslint-import-resolver-alias. It seems like the rule node/no-missing-import is not aware of ...

How to fix "resolve.alias" problem in Vite.js - Raul Melo

How to fix "resolve.alias" problem in Vite.js. This article was published on Jul 15, 2022, and takes approximately 2 minutes to read.

How to resolve a path alias in Storybook - +return

To solve this issue, we will need to configure Storybook's webpack to resolve the path alias. the concept is really similar to how...

Invalid webpack resolve alias

When overriding config.resolve.alias incorrectly in next.config.js webpack will throw an error because private-next-pages is not defined.

How to Create a Path Alias in Webpack

Establish the Module Aliases · Open your Webpack.config.js file. · If it's not already there, add a resolve property to the configuration object...