72 open SCSS issues currently match the default 10+ star filter. Scored difficulty: 5,947 at 1/5, 8,788 at 2/5, 12,702 at 3/5, 12,124 at 4/5, 857 at 5/5. This hub uses the same feed as the homepage, limited to repositories whose GitHub language is SCSS.
All languages · Browse projects · How to find good first issues
Unique repos with open help-wanted issues updated in the last 30 days
Showing 30 of ~72 matching filters (SCSS · 10+ stars)
ListThis issue requests an update to the website to reflect the current number of contributors, changing it from 3,000 to 4,000. The change appears to be a simple text or data update within the site's content.
This issue involves replacing a custom pagination implementation on the icons search documentation page with the official pagination component from the design system. The goal is to ensure all existing pagination functionality, including navigation, button behavior, scrolling, and synchronization between upper and lower components, remains intact after the replacement.
This issue proposes adding an automated behavioral test for the built JavaScript bundle of USWDS. This test is crucial for ensuring the integrity of the JS bundle, especially before a planned bundler replacement, as current CI processes do not verify its runtime behavior.
This issue proposes four low-risk tooling hygiene fixes in preparation for an upcoming ESM migration. The changes aim to ensure CI results are trustworthy by standardizing dependency installation with `npm ci`, removing unused test files, and addressing potential linting scope issues. These updates are crucial for accurately tracking the impact of the ESM migration.
A typo has been identified in the error message of the USWDS modal component. Specifically, 'aria-desribedby' is misspelled and should be 'aria-describedby' on line 227 of the modal's JavaScript file.
This issue proposes adding an automated test to verify the `package.json`'s `exports` map in the USWDS JavaScript package. The test will simulate how consumers import modules to ensure the exported paths resolve correctly, acting as a safety net for future changes that repoint exports from source to built artifacts.
This issue proposes implementing automated checks for new Pull Requests using GitHub Actions. The primary goal is to ensure that deployments using Hugo are successful, with an optional integration with Vercel for preview deployments if needed.
The user is reporting an issue where the `<html>` element in Paper CSS has a white background even when dark mode is enabled. They suggest adding a default background color to the `<html>` element using a CSS variable to resolve this.
This issue proposes implementing a feature to use media queries to serve different favicons for dark mode, inspired by a CSS-Tricks article. While currently only supported in Chrome, it's suggested as a potential future solution for broader color mode switching.
This bug report describes an issue where button text can be cut off if it's too long, leading to unreadable content. The expected behavior is to implement a better strategy, such as making the button text scrollable or multi-line, to ensure readability and accessibility, even if it slightly impacts the UI. The fix requires handling long single words, ensuring multiline text is readable, and maintaining stable icon sizes.
This issue proposes replacing the unreliable, mocha-based build test with a deterministic smoke test in the release preparation workflow. The new test will verify the presence of the correct version string in CSS files and ensure the compiled CSS is not empty, preventing releases with faulty builds.
The SCSS file `_typography.scss` contains duplicate and conflicting `details` rule blocks. This leads to unexpected styling due to source order precedence and bloats the compiled CSS. The fix involves removing one of the duplicate blocks, likely the earlier one, to ensure consistent styling and reduce file size.
This issue proposes replacing deprecated `MediaQueryList.addListener()` and `.removeListener()` methods with the standard `addEventListener()` and `removeEventListener()` in the `usa-footer` package. This change is necessary because the older methods are deprecated and `MediaQueryList` now inherits from `EventTarget`, making the standard methods universally supported in the project's target browsers.
This issue proposes adding the "type": "module" field to the root package.json to standardize JavaScript module handling within the repository. This change is internal and won't affect consumers, but requires updating Vite configuration files to correctly handle the new module type and removing redundant per-directory package.json files.
This issue proposes renaming several Node.js CommonJS tooling files to use the `.cjs` extension. The goal is to explicitly declare their module format by filename, rather than relying on the absence of a `"type": "module"` field in `package.json`. This is an optional, purely cosmetic change that does not affect functionality and can be done at any time.
This issue is the final step in the CommonJS-to-ESM migration for USWDS JavaScript. It involves removing an obsolete Storybook transform plugin, enforcing stricter linting rules that were relaxed during the migration, and updating outdated documentation. The work is dependent on other specific migration issues being merged and released.
This issue is the second part of a larger effort to convert JavaScript modules in the uswds-core package from CommonJS to ESM. It specifically targets remaining 'leaf' utility modules and a shared test helper, requiring adherence to strict conversion rules and dependencies on previously merged issues.
This issue is part one of a two-part effort to migrate six core JavaScript utility modules from CommonJS to ESM. It requires specific preceding issues to be merged and released, and adheres to strict conversion rules for imports and destructuring to ensure compatibility with both CommonJS and ESM targets.
This issue involves converting two JavaScript files (`config.js` and `events.js`) from CommonJS to ESM format within the USWDS project. The goal is to add named exports alongside existing default exports, as part of a larger migration effort. Crucially, existing code that uses default imports should not be refactored to use named imports.
This issue involves converting four JavaScript utility modules (`focus-trap`, `select-or-matches`, `toggle-form-input`, `validate-input`) and their tests from CommonJS to ESM. This is part of a larger migration effort and has specific prerequisites regarding other merged issues and package export configurations.
This issue is part of a larger migration to convert USWDS JavaScript components from CommonJS to ESM. Specifically, it requires converting the `usa-skipnav` and `usa-table` components and their tests. Developers must adhere to strict conversion rules and ensure a prerequisite issue is merged and released before starting.
This issue involves converting three JavaScript components (`usa-character-count`, `usa-footer`, and `usa-search`) from CommonJS to ESM. This is part of a larger migration effort and requires careful adherence to specific conversion rules to ensure compatibility with both CommonJS and ESM modules.
This issue is part of a larger effort to migrate the USWDS JavaScript codebase from CommonJS to ECMAScript Modules (ESM). Specifically, it requires converting the source code and tests for the `usa-accordion`, `usa-banner`, and `usa-button` components to ESM. Developers must adhere to specific conversion rules and ensure prerequisite issues are merged and released before starting.
This issue is part of a larger migration to convert the USWDS JavaScript components from CommonJS to ESM. Specifically, it requires converting the source code and tests for `usa-range`, `usa-tooltip`, and `usa-validation` to use ESM syntax. Developers must adhere to specific conversion rules and ensure a prerequisite issue is merged and released before starting.
This issue is part of a larger migration to convert USWDS JavaScript components from CommonJS to ESM. Specifically, it requires converting the `usa-input-mask` and `usa-language-selector` components and their tests. Developers must ensure a prerequisite issue related to package exports is merged and released before starting, and follow specific conversion rules for imports.
This issue involves converting three specific JavaScript components (usa-password, usa-file-input, and usa-in-page-navigation) from CommonJS to ESM. This is part of a larger migration effort to modernize the codebase. Developers must adhere to specific conversion rules and ensure a prerequisite issue is merged before starting.
This issue is part of a larger migration to convert the USWDS JavaScript components from CommonJS to ESM. Specifically, it requires converting the `usa-header` component's source and tests, as well as the spec files for `usa-nav`. Developers must wait for another specific issue (#6852) to be merged and released before starting this task.
This issue is part of a larger migration to convert JavaScript components from CommonJS to ESM. Specifically, it requires converting the `usa-combo-box` and `usa-modal` components and their tests to ESM. This needs to be done in a single pull request to avoid breaking the build process due to interdependencies between these two components.
This issue involves converting the `usa-date-picker` JavaScript component from CommonJS to ESM. It's part of a larger migration effort and requires specific steps to ensure compatibility with existing consumers, including adding named re-exports for certain functions. The conversion should only begin after a related package export issue has been merged and released.
This issue involves converting the `usa-time-picker` JavaScript component from CommonJS to ESM. It's part of a larger migration effort and has specific prerequisites regarding package exports and dependencies that must be addressed first. The conversion follows strict rules for handling imports and destructuring.
Also browsing: Python , TypeScript , JavaScript
