rtritto

Any update?

Correct ansi-regex is `.x` ([source1](https://www.npmpeer.dev/packages/ansi-regex/compatibility), [source2 ](https://nodejs.org/es/blog/npm/peer-dependencies)): ``` "@babel/core": "7.x", "@babel/preset-env": "7.x", "babel-loader": "8.x", "cypress": "*", "webpack": "5.x" ``` Should be consider instead to add `*` (accept all versions).

@rschristian thanks for answer. > Any reason why you're using `yarn add preact preact-render-to-string preact-ssr-prepass next-plugin-preact` I tried to create minimal steps to reproduce warnings. Command: `yarn add next next-plugin-preact...

I'm using latest yarn berry version (currently 3.0.2) with a clean project: 1. `yarn init -y` 2. `yarn set version berry` 3. `yarn add next next-plugin-preact preact preact-render-to-string react@npm:@preact/compat@* react-dom@npm:@preact/compat@*...

FYI @arcanis @merceyz

Thanks to all for answers. Same warnings log with yarn v1.22.11: 1. `yarn init -y` 2. `yarn add next next-plugin-preact preact preact-render-to-string react@npm:@preact/compat@* react-dom@npm:@preact/compat@* react-ssr-prepass@npm:preact-ssr-prepass@*` log ``` info No lockfile...

Conflict is generated because `eslint-plugin-import` is a dependency in: - `@ijsto/eslint-config` (needed by peerDependencies of `eslint-config-airbnb`) - `eslint-config-next` Probably, a possible solution in `@ijsto/eslint-config` is to add `eslint-config-next` and to...

Some duplicated dependencies in `eslint-config-next` to remove in `@ijsto/eslint-config` (they should conflict after removing `eslint-plugin-import`): - `eslint-plugin-jsx-a11y` - `eslint-plugin-react` - `eslint-plugin-react-hooks` Another interesting feature, gained with `eslint-config-next`, is the import...

By this way, `@ijsto/eslint-config` must install all peerDependencies of `eslint-config-next`: - `next` and (maybe) `typescript` from `eslint-config-next` - `react` and `react-dom` from `next` FYI - [Recommended Plugin Ruleset](https://nextjs.org/docs/basic-features/eslint#recommended-plugin-ruleset): >If you...

Same problem. Body content is returned as {} instead of correct value. ## Steps to reproduce 1. `yarn init -y` 2. `yarn set version berry` 3. `yarn add @elastic/ecs-winston-format triple-beam...