Fix: Your dependencies are out of date, otherwise you would be using a newer yaml than yaml@2.2.1. Try relocking your lockfile or deleting node_modules. If the problem persists, one of your dependencies may be bundling outdated modules.
Fix: Your dependencies are out of date, otherwise you would be using a newer yaml than yaml@2.2.1. Try relocking your lockfile or deleting node_modules. If the problem persists, one of your dependencies may be bundling outdated modules.
Introduced through: @singularit/eslint-config-react@1.1.0 Fixed in: yaml@2.2.2, @2.3.0-5
Detailed:
Introduced through: pricing-cockpit@0.1.0 › @singularit/eslint-config-react@1.1.0 › @singularit/eslint-config-typescript@1.2.0 › @singularit/eslint-config-basic@1.3.1 › yaml-eslint-parser@1.1.0 › yaml@2.2.1
Fix: Your dependencies are out of date, otherwise you would be using a newer yaml than yaml@2.2.1. Try relocking your lockfile or deleting node_modules. If the problem persists, one of your dependencies may be bundling outdated modules.
Introduced through: pricing-cockpit@0.1.0 › @singularit/eslint-config-react@1.1.0 › @singularit/eslint-config-typescript@1.2.0 › @singularit/eslint-config-basic@1.3.1 › eslint-plugin-yml@1.5.0 › yaml-eslint-parser@1.1.0 › yaml@2.2.1
Fix: Your dependencies are out of date, otherwise you would be using a newer yaml than yaml@2.2.1. Try relocking your lockfile or deleting node_modules. If the problem persists, one of your dependencies may be bundling outdated modules.