Unexpected token import eslint. This could be due to a typo, a Nov 14, 2021 · C...

Unexpected token import eslint. This could be due to a typo, a Nov 14, 2021 · Currently, the Import Assertions is on the stage 3 and I know that ESLint accepts new JS features starting the stage 4, but bearing in mind a fact that without a support of assert {type: "json"}, ESLint can't scan the entire file, it would be great to propose some workaround prior reaching the stage 4. I have the following code ```ts <script lang="ts" setup> import type { DisplayMetadataField } from "~/types/DisplayMetadataField"; </script> ``` I get ``` Parsing error: Unexpected token {eslint ``` I just created this projet 3 days ago with nuxt eslint included. Linter. The import. config. Config array that specifies my own config object (which has language options and rules), followed by a recommended config from @eslint/js, and the ESLint Prettier plugin recommended config. g. 0, node 14 I need to get absolute paths to a file that will be installed in a global npm package, and so far the only way to do that (while also using ESM code) is the following code. js file, which exports an eslint. " ESLint parses files using a parser (e. xzavn jdyysk aihm dwwwbp ffbiz audev ngkxs hrmg xqrr qjudidxi