better-regex autofix breaks regular expression syntax: /|/g -> //g
An empty regular expression such as // is invalid and parsed as a line comment instead, which breaks other syntax within the code. I would expect the better-regex rule to not propose code with empty regular expressions.
The following is a minimal example:
const expression = /|/;I would expect this expression to be corrected to something like:
const expression = /(?:)/;
sindresorhus / eslint-plugin-unicorn
More than 100 powerful ESLint rules
4.2k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too