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
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 broccoli-plugin@4.0.7
#945
opened Nov 30, 2023 by
ahayes91
Since 8.9.0, parsing is ignoring files outside the configuration file folder.
#939
opened Oct 24, 2023 by
giovannetti-eric
Doesn't parse files that have [] in the path (e.g., Next.js app directory with [lang]
#880
opened Aug 9, 2023 by
olikami
JS Lexer does not recognize keys in the options passed to
t
func
#779
opened Feb 17, 2023 by
rikmarais
The keyPrefix argument is ignored in JavascriptLexer, and not in JsxLexer
#737
opened Dec 21, 2022 by
ohardy
Empty Strings inside t function causes a false info of Added keys.
#634
opened Sep 22, 2022 by
christian1koch
failOnUpdate fails when no update happens, when using namespaces
Bug
#597
opened Jun 8, 2022 by
JulioC
Does not parse plural default values from Trans component
Bug
#580
opened May 27, 2022 by
addiebarron
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.