8000 Metro server not respecting default config for forwardClientLogs · Issue #1306 · facebook/metro · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Metro server not respecting default config for forwardClientLogs #1306
Open
@rubenspgcavalcante

Description

@rubenspgcavalcante

Already tried

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
No logs being outputted to console where metro process is running, seems the default server.forwardClientLogs (true) is not being respected. Adding explicitly the config

server: { forwardClientLogs: true }

will solve the issue and the logs will flow again, but this warning will start to show up:

● Validation Warning:

  Unknown option "server.forwardClientLogs" with value true was found.
  This is probably a typing mistake. Fixing it will remove this message.

If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can yarn install and yarn test.
Private source (company app), can't provide it here :(

What is the expected behavior?
The default config work, or if we pass the config forwardClientLogs explicitly, don't have this warning being shown.

Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.

  • Metro v0.80.9, metro-config v0.80.1 with default config being merged from @react-native/metro-config v0.73.5

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0