-
-
Notifications
You must be signed in to change notification settings - Fork 42
[bug] error-boundaries false positives on non-react code #1690
Copy link
Copy link
Closed
Description
Describe the bug
I have two questions:
- Am I allowed to run
@eslint-reacton non-react files?
If no, you can ignore this report.
Reproduction
import passport from 'passport';
try {
const { getAzureStrategy } = await import('./ee/auth/azure/index.js');
passport.use(getAzureStrategy());
} catch (err) {
logger.error('Error initializing PrairieLearn server:', err);
throw err;
}Expected behavior
No error
Platform and versions
Node 24, eslint-react v4, eslint v10
Stack trace
Use an Error Boundary instead of try/catch around the 'use' hook. The 'use' hook suspends the component, and its errors can only be caught by Error Boundaries.
@eslint-react/error-boundaries
Additional context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels