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

[Feature] Regular update of Browserslist #824

Open
1 task
Queen-codes opened this issue Oct 7, 2024 · 5 comments
Open
1 task

[Feature] Regular update of Browserslist #824

Queen-codes opened this issue Oct 7, 2024 · 5 comments
Labels
🤖 aspect: dx Concerns developers' experience with the codebase ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@Queen-codes
Copy link

Problem

While running the project locally, a warning comes up that caniuse-lite is outdated. This warning suggests that the Browserslist is not up to date, which could lead to outdated browser compatibility checks during development. This could maybe cause issues with browser support, especially as new features are released.

Description

The feature would involve regularly updating the Browserslist database to keep it current with the latest browser compatibility.
This can be done by running the following command: `npx update-browserslist-db@latest

`
This feature can be implemented;
-By adding the update command to the documentation and or Readme as a step for contributors to run periodically as many might skip during development

-by integrating it into the deployment pipeline to automatically check and update the browserslist db when necessary.

Additional context

See more - Why you should update broswerDb list regularly

Screenshot 2024-10-07 at 14 20 43

Implementation

  • I would be interested in implementing this feature.
@Queen-codes Queen-codes added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Oct 7, 2024
@TimidRobot TimidRobot added 🚧 status: blocked Blocked & therefore, not ready for work 🤖 aspect: dx Concerns developers' experience with the codebase and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 💻 aspect: code Concerns the software code in the repository labels Oct 7, 2024
@TimidRobot
Copy link
Member

TimidRobot commented Oct 7, 2024

@Queen-codes This is a great write-up/issue! Thank you!

🚧 status: blocked Blocked & therefore, not ready for work : This issue can be closed or updated after this project is migrated to the current Vocabulary design system.

After migration, I expect the autoprefixer package (which requires autoprefixer which requires caniuse-lite) will no longer be used.

@Tharanishwaran
Copy link

can i work on this issue ?

@Queen-codes
Copy link
Author

Thank you for the feedback @TimidRobot

@Queen-codes
Copy link
Author

Queen-codes commented Oct 7, 2024

can i work on this issue ?

hi. @Tharanishwaran. this issue is currently blocked and should be closed or updated after migration to the current Vocabulary design system according to @TimidRobot

@Tharanishwaran
Copy link

hi. @Queen-codes thankyou for the information

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 aspect: dx Concerns developers' experience with the codebase ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

3 participants