Run lingui extract for specified files
See original GitHub issueIs your feature request related to a problem? Please describe.
I am trying to run lingui extract
in CI steps to warn developer if they forget to run lingui extract
. However running lingui extract
over the entire project takes ~10mins
Describe the solution you’d like
lingui extract
should take an optional glob that narrow down the list of files the command run on
Describe alternatives you’ve considered lingui v3 seems to include a watch option. Maybe this is related?
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:17 (12 by maintainers)
Top Results From Across the Web
Working with LinguiJS CLI
@lingui/cli provides the lingui command for extracting, merging and compiling message catalogs. Follow setup instructions to install required packages.
Read more >lingui/js-lingui - Gitter
I want to create a new syntax for specifying messages to be extracted. ... strings disappeared from the messages.json files when running lingui...
Read more >@lingui/babel-plugin-transform-react | Yarn - Package Manager
Babel plugin which transforms content of components from lingui-react to ICU ... All notable changes to this project will be documented in this...
Read more >Localizing JavaScript & React Apps with LinguiJS | Phrase
However, Lingui makes extraction and compilation really ... the package and start running the CLI commands to work with translation files.
Read more >How to set up internationalization in React using Lingui.js
js will extract messages from these files and write them inside the language-specific folder. Each language (e.g., English, Urdu, Chinese, etc.,) ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I could work on it this week at night, lets go
I think I fixed this issue with two lines of code … I’ll create a pull request once correctly tested
Some performance testing:
New version with files param:
yarn extract src 1.47s user 0.26s system 111% cpu 1.709 total
Actual code branch without files filter:
yarn extract 4.19s user 0.33s system 135% cpu 3.345 total