Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[@wordpress/stylelint-config] The premise of "@21.24.0", "Stylelint" is out of date. #54127

Closed
stein2nd opened this issue Sep 2, 2023 · 0 comments · Fixed by #64828
Closed
Labels
[Tool] stylelint config /packages/stylelint-config [Type] Enhancement A suggestion for improvement.

Comments

@stein2nd
Copy link

stein2nd commented Sep 2, 2023

Description

The premise of "@wordpress/stylelint-config@21.24.0", "Stylelint", is out of date. Wouldn't it be better to at least cover "stylelint@"^15.10.3"?

Step-by-step reproduction instructions

none

Screenshots, screen recording, code snippet

image

Environment info

System:

  • OS: macOS 13.5.1
  • CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  • Memory: 219.47 MB / 32.00 GB
  • Shell: 3.2.57 - /bin/bash

Binaries:

  • Node: 20.5.1 - ~/.nodebrew/current/bin/node
  • Yarn: 1.22.19 - ~/.nodebrew/current/bin/yarn
  • npm: 10.0.0 - ~/.nodebrew/current/bin/npm
  • pnpm: 8.6.12 - ~/.nodebrew/current/bin/pnpm

npmPackages:

  • @wordpress/scripts: ^26.12.0 => 26.12.0

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes

@jordesign jordesign added [Type] Enhancement A suggestion for improvement. [Package] E2E Tests /packages/e2e-tests labels Sep 4, 2023
@Mamaduka Mamaduka added [Tool] stylelint config /packages/stylelint-config and removed [Package] E2E Tests /packages/e2e-tests labels May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Tool] stylelint config /packages/stylelint-config [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants