Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"cli extract" fails when I do not use macro and have no babel macro package installed
See original GitHub issueDescribe the bug
I’m using Next.js. I do not need macros, so I decided not to install @babel/macro etc. I did it because I want Next.js to use SWC.
To Reproduce
Create a minimal Next.js project.
Do not install anything related to macros.
Run yarn extract.
Console logs gets lots of warnings - lingui-extract.js tries to use babel-plugin-macros.
Expected behavior
extract/compile should work without babel-plugin-macros dependency.
Additional context
-
jsLingui version
3.13.2 -
Your Babel config (e.g.
.babelrc) - Next.js; no custom babelrc config.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
What’s the idea behind automatically closing issues that are not rejected explicitly? If nobody can take care of it now, it does not mean the issue automagically becomes irrelevant or not actual. It is still actual.
This won’t get done ever. We use babel-plugin-macros for extracting the t``. Until SWC opens a way to interact with the AST code we CAN’T do nothing.