Bug: Unable to parse line in .flowconfig file

[TajAlasfiyaa]

Bug Description

When running Flow on the dom-node, test, and dom-node-webpack renderers, an error message appears:

.flowconfig:326 Unable to parse line.
Flow failed for the test renderer

error Command failed with exit code 8.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

The same error occurs when running yarn flow dom-node:

.flowconfig:171 Unable to parse line.
Flow failed for the dom-node renderer

error Command failed with exit code 8.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Steps to Reproduce

1. Run yarn flow.
2. Follow the instructions to select a primary renderer.
3. Run yarn flow test.
4. Expected Behavior

Flow should run successfully on the test renderer.

Actual Behavior

Flow fails with the error message .flowconfig:326 Unable to parse line.

Workaround

Currently, there is no known workaround for this issue.

Additional Information

• Yarn version: 1.22.19
• Node.js version: v20.9.0
• Windows version : 11 23H2

[vlad-a-barbu]

Had a similar issue recently on a Windows laptop due to the default CR-LF line endings. When my .flowconfig was generated (through /scripts/flow/createFlowConfigs.js), replacements on the initial template assumed LF line endings. If you check your .flowconfig, it's likely that some variables are not replaced correctly because of this.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!