Shouldn't `userEvent` be only exported as a named export ? #1205

mlz11 · 2024-04-04T15:17:29Z

mlz11
Apr 4, 2024

Hey everyone 👋🏻

Could someone help me understand what's the point of exporting userEvent as a default export and as a named export ?

export { userEvent as default } from './setup';
export { userEvent } from './setup';
export type { UserEvent } from './setup/setup';
export type { keyboardKey } from './system/keyboard';
export type { pointerKey } from './system/pointer';
export { PointerEventsCheckLevel, type Options } from './options';

Using automatic import I get the following which triggers the following ESLint rule eslintimport/no-named-as-default

import userEvent from '@testing-library/user-event'; 
// ESLint expects 'import { userEvent } from '@testing-library/user-event';'

Answered by mlz11

Apr 5, 2024

Got the answer on Twitter ⬇️

View full answer

mlz11 · 2024-04-05T08:21:11Z

mlz11
Apr 5, 2024
Author

Got the answer on Twitter ⬇️

0 replies

ahayes91 · 2025-03-19T11:30:50Z

ahayes91
Mar 19, 2025

https://testing-library.com/docs/user-event/intro/ examples currently use the default export instead of named, probably needs a quickie PR to fix - testing-library/testing-library-docs#1476

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Shouldn't `userEvent` be only exported as a named export ? #1205

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Shouldn't userEvent be only exported as a named export ? #1205

mlz11 Apr 4, 2024

Replies: 2 comments

mlz11 Apr 5, 2024 Author

ahayes91 Mar 19, 2025

Shouldn't `userEvent` be only exported as a named export ? #1205

mlz11
Apr 4, 2024

mlz11
Apr 5, 2024
Author

ahayes91
Mar 19, 2025