Closed moorejs closed 6 months ago
Apparently undefined
is parsed as an identifier, not a literal (like null
and others) 😭 no matter how much I work with JavaScript it still manages to surprise me sometimes!
I'll just need to add a check in trace
. Thanks for the issue!
Describe the bug
When I use
undefined
as my initial value forcreateEffect
, eslint crashes in rulesolid/no-react-deps
.To Reproduce
Expected behavior
The plugin does not crash. The warning does not apply.
Environment (please complete the following information):
node --version
): 20.5.1eslint-plugin-solid
version (npm list eslint-plugin-solid
/yarn why eslint-plugin-solid
): 0.13.0eslint
version (npm list eslint
/yarn why eslint
): 8.53.0Additional context
Stack trace points to the
trace
function.