import-js/eslint-plugin-import

Possible false positive import/namespace error on exported type

Open

Aperta il 22 giu 2024

Vedi su GitHub
 (5 commenti) (0 reazioni) (0 assegnatari)JavaScript (4946 star) (1540 fork)batch import
bughelp wantedtypescript

Descrizione

I'm seeing the following ESLint error when trying to use a namespace import for React Aria Components. I'm unsure whether this could be related to the config in the default .eslintrc.cjs file of the Remix template or if it might be a false positive being reported. ButtonProps is being exported by the RAC module, so it's confusing why this error would be shown.

'ButtonProps' not found in imported namespace 'ReactAria'. eslint(import/namespace)

import * as ReactAria from "react-aria-components";

// ...

export interface ButtonProps
  extends ReactAria.ButtonProps,
    VariantProps<typeof buttonVariants> {}

// ...

The error is not reported when I use the namespace import for exports that aren't types:

<ReactAria.Button {...props} />

Running npm run lint in the example app will show the error mentioned above.

Any ideas what might be happening here and whether this is expected or not?

Guida contributor

Tech stack
javascripttypescriptnodejs
Dominio
toolingdeveloper experience
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
half day
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
ESLintTypeScripteslint plugin import
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
50
Direzione di ricerca
Investigate the `import/namespace` rule in the eslint plugin import repository. Focus on how the rule resolves namespace imports for type only exports. Check the default Remix `.eslintrc.cjs` for any relevant settings. Review the `react aria components` exports for `ButtonProps` to confirm it is exported as a type. Consider if the issue is rooted in the rule's handling of `export type` versus `export`. Reproduction steps are provided in a StackBlitz example.