-
-
Notifications
You must be signed in to change notification settings - Fork 202
Issues: i18next/i18next-parser
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Warn when JSX key attribute is "SyntaxKind.ConditionalExpression"
#1092
opened Dec 3, 2024 by
trevorharwell
Script globally catches error and outputs a generic disclaimer rather than printing a useful error
#1039
opened Aug 2, 2024 by
Jme797
[DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
#1019
opened Jul 5, 2024 by
Zerebokep
Keys not being extracted when comment is inside React components
#988
opened Mar 13, 2024 by
Myzel394
Incorrect extraction for multiple
useTranslation
on the same page
#973
opened Feb 19, 2024 by
affanshahid
New high severity vulnerability from
inflight
, coming from [email protected]
#945
opened Nov 30, 2023 by
ahayes91
Doesn't parse files that have [] in the path (e.g., Next.js app directory with [lang]
#880
opened Aug 9, 2023 by
olikami
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.