Bug no-unpublished-bin: false positive with files starting with ./

[regseb]

Description

The no-unpublished-bin rule returns false positives when the paths of the files property (in package.json) begin with "./".

Files

• package.json

  {
      "name": "testcase",
      "version": "1.0.0",
      "type": "module",
      "private": true,
      "bin": "./index.js",
      "files": ["./index.js"],
      "dependencies": {
          "eslint": "8.42.0",
          "eslint-plugin-n": "16.0.0"
      }
  }

• eslint.config.js

  import n from "eslint-plugin-n";
  
  export default [
      {
          plugins: { n },
          rules: { "n/no-unpublished-bin": "error" },
      },
  ];

• index.js

  console.log("Hello world");

To reproduce

1. npm install
2. npx eslint index.js

/home/regseb/testcase/index.js
  1:1  error  npm ignores 'index.js'. Check 'files' field of 'package.json' or '.npmignore'  n/no-unpublished-bin

✖ 1 problem (1 error, 0 warnings)

Additional information

With the value { "files": ["index.js"] }, ESLint doesn't report any errors.

[regseb]

I don't reproduce the problem with eslint-plugin-n 16.2.0. This pull request #123 (which fixes #122) certainly corrected the problem.

[scagood]

Thank you for testing and confirming 😀