fixbug:resolve parse errors

[hanxinhenxue]

Description

When I used eslint9, I wanted to introduce an unplugin auto import eslint that ignored the file and changed the configuration file path to a file ending in. cjs or. mjs. The file was generated successfully, but the project reported an error and could not run. After debugging, it was found that the error was caused by using the JSON. parse method to parse these two formats of files

Linked Issues

Additional context

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[VisionBao]

Same issue for me, hope it can be fixed quickly

[VisionBao]

Is there anyone who can pay attention to this issue? @antfu @userquin

[antfu]

This is not a safe assumption. I'd say we ignore parsing in non-json mode.

[VisionBao]

In my case.I can't use JSON format files in my eslint.config.js file. So, I'll go with the CJS format for my setup. Our plugin works great when exporting JSON, but as soon as I switch to CJS, it runs into problems and crashes.

Even though it doesn't affect my code running, it does cause ESLint to throw errors.

env:
"eslint": "^9.3.0",

export default [
  {
    files: ['**/*.{js,vue}'],
    languageOptions: {
      globals: {
        ...globals.browser,
        ...globals.node,
        ...autoImportConfig.globals,     <-------
      },
      parser: vueEslintParser,
      parserOptions: {
        ecmaVersion: 2020,
        sourceType: 'module',
      },
    },
    plugins: {
      vue: pluginVue,
      prettier: prettierPlugin,
    },
    settings: {},
    rules: {
      ...pluginJs.configs.recommended.rules,
      ...pluginVue.configs['flat/essential'].rules,
      'prettier/prettier': 'error',
    },
  },
  {
    rules: {
      ...prettier.rules,
    },
  },
];