Open Goldziher opened 4 months ago
NPM warnings:
npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: eslint-plugin-typescript-sort-keys@3.1.0 npm WARN Found: @typescript-eslint/parser@7.0.1 npm WARN node_modules/@typescript-eslint/parser npm WARN dev @typescript-eslint/parser@"^7.0.1" from the root project npm WARN 2 more (@tool-belt/eslint-config, @typescript-eslint/eslint-plugin) npm WARN npm WARN Could not resolve dependency: npm WARN peer @typescript-eslint/parser@"^6" from eslint-plugin-typescript-sort-keys@3.1.0 npm WARN node_modules/eslint-plugin-typescript-sort-keys npm WARN eslint-plugin-typescript-sort-keys@"^3.1.0" from @tool-belt/eslint-config@5.2.0 npm WARN node_modules/@tool-belt/eslint-config npm WARN npm WARN Conflicting peer dependency: @typescript-eslint/parser@6.21.0 npm WARN node_modules/@typescript-eslint/parser npm WARN peer @typescript-eslint/parser@"^6" from eslint-plugin-typescript-sort-keys@3.1.0 npm WARN node_modules/eslint-plugin-typescript-sort-keys npm WARN eslint-plugin-typescript-sort-keys@"^3.1.0" from @tool-belt/eslint-config@5.2.0 npm WARN node_modules/@tool-belt/eslint-config npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: 'chatbot@1.0.0', npm WARN EBADENGINE required: { npm WARN EBADENGINE yarn: 'please-use-npm', npm WARN EBADENGINE npm: '>=[10](https://github.com/basemind-ai/bot/actions/runs/7955880378/job/21715588591#step:4:11).4.0', npm WARN EBADENGINE pnpm: 'please-use-npm', npm WARN EBADENGINE node: '>=v20.0.0' npm WARN EBADENGINE }, npm WARN EBADENGINE current: { node: 'v20.[11](https://github.com/basemind-ai/bot/actions/runs/7955880378/job/21715588591#step:4:12).0', npm: '10.2.4' } npm WARN EBADENGINE } npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
Hi 🙂 We are also experiencing this issue while trying to upgrade the ESLint monorepo to v7. Checkout this merge request for more details: https://gitlab.com/biomedit/next-widgets/-/merge_requests/323.
Same here.
NPM warnings: