You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
Rome encountered an unexpected error
This is a bug in Rome, not an error in your code, and we would appreciate it if you could report it to https://github.com/rome/tools/issues/ along with the following information to help us fixing the issue:
Source Location: crates/rome_js_analyze/src/analyzers/nursery/use_simple_number_keys.rs:92:14
Thread Name: rome::worker_12
Message: called `Option::unwrap()` on a `None` value
Note: I enabled all rules in rome.json.
One of the codes that produces the issue:
export function Config(generator) {
return { generator }
}
This also crashes the playground.
Expected result
No error
Code of Conduct
I agree to follow Rome's Code of Conduct
The text was updated successfully, but these errors were encountered:
I believe this issue shouldn't block the release because it's a nursery rule, and it makes sense if they are buggy. Although, it's a valid bug we should fix!
That's true. However, I could like to get a "stable" user experience even with nursery rules :) I will fix it before the release, except if someone is interested to take this issue :)
Conaclos
changed the title
🐛 UseSimpleNumberKeys unwrap error
🐛 useSimpleNumberKeys unwrap error
May 10, 2023
Environment information
What happened?
I got the following error numerous times:
Note: I enabled all rules in
rome.json
.One of the codes that produces the issue:
This also crashes the playground.
Expected result
No error
Code of Conduct
The text was updated successfully, but these errors were encountered: