Bug: pnpm exec eslint didn't work on Mac os

Environment

Environment Info:

Node version: v16.17.0 npm version: v8.15.0 pnpm version: v7.9.5 Local ESLint version: v8.23.0 (Currently used) Global ESLint version: Not found Operating System: darwin 21.6.0

What parser are you using?

Default (Espree)

What did you do?

Configuration

//eslint.config.js
export default [
  {
    rules: {
      semi: "warn",
      "prefer-const": "error",
    },
  },
];

//Missing semicolon
Vue.use(PiniaVuePlugin)

What did you expect to happen?

config script in package.json

"lint": "eslint src/**/*.js",

run pnpm run lint terminal print nothing.

run pnpm exec eslint src/**/*.js, output:

/Users/zhanglolo/Documents/vscodeProjects/vue2-vite-pinia-vitest-demo/src/main.js
  9:24  warning  Missing semicolon  semi

✖ 1 problem (0 errors, 1 warning)
  0 errors and 1 warning potentially fixable with the `--fix` option.

What actually happened?

It seem like eslint didn’t work by using package.json script.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

[mdjermanovic]

Does it work as expected now (i.e. does it report the semi warning in src/main.js when you run the package.json lint script)?

Yes! but, what makes me confuses is pnpm run lint (npm run lint) get different out put eslint:cli CLI args: [...] from pnpm exec eslint src/**/*.js(npx eslint src/**/*.js).

Then I think we can close this issue since eslint correctly resolves the glob when the glob is passed into eslint. The difference between the lists of files to which the glob is expanded before calling eslint might be a good question for npm/pnpm, as eslint has no control over it. ESLint’s Command Line Interface documentation suggests using quotes for consistent behavior:

Please note that when passing a glob as a parameter, it will be expanded by your shell. The results of the expansion can vary depending on your shell, and its configuration. If you want to use node glob syntax, you have to quote your parameter (using double quotes if you need it to run in Windows), as follows

[zhanglolo]

Does it work as expected now (i.e. does it report the semi warning in src/main.js when you run the package.json lint script)?

Yes! but, what makes me confuses is pnpm run lint (npm run lint) get different out put eslint:cli CLI args: [...] from pnpm exec eslint src/**/*.js(npx eslint src/**/*.js).

May be npm have do something stuff.🤨