Node Warning Mitigation

Context

Use this when a Node warning appears during local tooling startup (Playwright, Storybook, CLI wrappers) and the trace points into node_modules rather than project code.

Patterns

• Reproduce the warning with the upstream tool started directly, outside any repo wrapper like Playwright webServer, before changing project config.
• Use node --trace-deprecation <tool-entrypoint> or an equivalent targeted trace to identify the exact package and call site.
• Decide whether the repo actually owns the root cause. If the trace lands in vendored tooling, prefer documenting the warning and keeping it visible unless a safe package upgrade or repo-controlled reconfiguration removes it.
• Only land a warning-related change when it is a real root-cause fix (for example, upgrading to a compatible package version or removing a repo-owned unsafe invocation).
• Validate the affected startup/test path after the investigation so the team knows whether the warning is harmless noise or coupled to a failing workflow.

Examples