How to handle upstream-only Node deprecation noise without hiding real warnings
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.
webServer, before changing project config.node --trace-deprecation <tool-entrypoint> or an equivalent targeted trace to identify the exact package and call site.src/UmbracoPrism.Client/package.jsonsrc/UmbracoPrism.Client/playwright.config.tssrc/UmbracoPrism.Client/node_modules/@storybook/core/dist/common/index.cjscd src/UmbracoPrism.Client && npm run storybook -- --quiet --smoke-testcd src/UmbracoPrism.Client && node node_modules/.bin/playwright test --reporter=line--disable-warning or --no-warnings when the underlying package issue still exists.node_modules files to stop a warning.