Chalk with ESLint & Airbnb Base

I am using the latest version of Chalk and using ESLint with the Airbnb Base. Unfortunately, when I import chalk, am getting the following linting error: Unable to resolve path to module ‘chalk’. eslint(import/no-unresolved)

The module loads and works fine but it is throwing that linting error and it is driving me nuts.

package.json for DevDependencies and ESLint config:

  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^5.13.0",
    "@typescript-eslint/parser": "^5.13.0",
    "eslint": "^8.10.0",
    "eslint-config-airbnb-base": "^15.0.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-plugin-import": "^2.25.4",
    "eslint-plugin-prettier": "^4.0.0",
    "nodemon": "^2.0.15",
    "prettier": "^2.5.1",
    "typescript": "^4.6.2"
  },
  "eslintConfig": {
    "extends": [
      "airbnb-base",
      "plugin:@typescript-eslint/recommended",
      "plugin:prettier/recommended"
    ],
    "env": {
      "node": true
    }
  },

app.js where I call Chalk:

import express, { json, urlencoded } from 'express';
import helmet, { contentSecurityPolicy } from 'helmet';
import morgan from 'morgan';
import Debug from 'debug';
import chalk from 'chalk';

console.log(`${chalk.red('Hello!'});

I could use some guidance as to why it’s throwing this for Chalk. I am not getting that error for my other Packages. Thanks!

[jmcombs]

@Qix- it looks like the issue is because "main": "./source/index.js", is missing from package.json.

	"repository": "chalk/chalk",
	"funding": "https://github.com/chalk/chalk?sponsor=1",
	"type": "module",
	"main": "./source/index.js",
	"exports": "./source/index.js",

Once main is added to package.json linting passes.

The linting error pops up due to package import-js/eslint-plugin-import. There is an open issue Rule import/no-unresolved raise false positive when there is no main field in the package.json #2132 but the maintainer of that package is adamant that proper etiquette is to include both main and exports in package.json. Main entry point export has also been referenced as justification for this requirement from the NodeJS website.

Is this something you would be willing to add or would you prefer me to submit a PR with a fix? (I am new to this)

[sindresorhus]

https://github.com/chalk/chalk/releases/tag/v5.0.1