You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When running formatjs extract with the --throws option, it would appear TypeScript fails in some way, but what it fails on is unclear.
Error: Debug Failure. Output generation failed
at Object.transpileModule (/Users/austinbratcher/Development/Projects/ShipStation/shipstation-ui/node_modules/typescript/lib/typescript.js:123670:29)
at processFile (/Users/austinbratcher/Development/Projects/ShipStation/shipstation-ui/node_modules/@formatjs/cli/src/extract.js:104:26)
at /Users/austinbratcher/Development/Projects/ShipStation/shipstation-ui/node_modules/@formatjs/cli/src/extract.js:151:59
at step (/Users/austinbratcher/Development/Projects/ShipStation/shipstation-ui/node_modules/@formatjs/cli/src/extract.js:44:23)
at Object.next (/Users/austinbratcher/Development/Projects/ShipStation/shipstation-ui/node_modules/@formatjs/cli/src/extract.js:25:53)
at fulfilled (/Users/austinbratcher/Development/Projects/ShipStation/shipstation-ui/node_modules/@formatjs/cli/src/extract.js:16:58)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Describe the solution you'd like
When an exception is thrown from TypeScript failing to transpile a module, it would be helpful if the exception included more actionable information to help debug the issue. Something along the line of including the specific file that failed if that's possible.
Describe alternatives you've considered
Such a problem could be solved "manually" by writing a script to parse each file in the project individually and seeing what fails. This is a less that desirable solution in my opinion.
Additional context
If I do not include the --throws flag, extraction simply completes with warnings, but those warnings also do not include actionable information.
The text was updated successfully, but these errors were encountered:
Which package?
cli
Is your feature request related to a problem? Please describe.
When running
formatjs extract
with the--throws
option, it would appear TypeScript fails in some way, but what it fails on is unclear.Example CLI call:
Example output of thrown exception:
Describe the solution you'd like
When an exception is thrown from TypeScript failing to transpile a module, it would be helpful if the exception included more actionable information to help debug the issue. Something along the line of including the specific file that failed if that's possible.
Describe alternatives you've considered
Such a problem could be solved "manually" by writing a script to parse each file in the project individually and seeing what fails. This is a less that desirable solution in my opinion.
Additional context
If I do not include the
--throws
flag, extraction simply completes with warnings, but those warnings also do not include actionable information.The text was updated successfully, but these errors were encountered: