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

Epic: Transition SASS to using the module system instead of imports #329

Open
53 tasks
pyrello opened this issue Oct 16, 2020 · 2 comments · May be fixed by #954
Open
53 tasks

Epic: Transition SASS to using the module system instead of imports #329

pyrello opened this issue Oct 16, 2020 · 2 comments · May be fixed by #954
Labels
4.x 4.x version story A story is a collection of tasks that resolve a need for a specified set of stakeholders.

Comments

@pyrello
Copy link
Contributor

pyrello commented Oct 16, 2020

https://css-tricks.com/introducing-sass-modules/

Problem

The import system in SASS is being deprecated in favor of a new module system with use syntax.

Proposed solution

Migrate all the SASS files to using this new system. Each component or asset file should have it's own issue, as this will be a lengthy project and take a while.

src/assets/scss

src/components

@pyrello pyrello added the story A story is a collection of tasks that resolve a need for a specified set of stakeholders. label Oct 16, 2020
@joewhitsitt
Copy link
Contributor

https://sass-lang.com/blog/the-module-system-is-launched details EOL and possible migration techniques

@pyrello
Copy link
Contributor Author

pyrello commented May 26, 2022

Need to check out if we can do this yet in 4.x branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x 4.x version story A story is a collection of tasks that resolve a need for a specified set of stakeholders.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants