You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many projects use Sass, but many do not. The cvi-styles package right now can only be consumed as a bunch of Sass files that assume presence of Sass as a dependency in an app that employs that library.
However this should not be mandatory since it could be perfectly fine to simply utilise CSS classes and CSS variables coming from the library. An app should be able to employ vanilla CSS, PostCSS, Less or something else and enjoy the CVI library at the same time.
Precompiled styles should be offered as one CSS file.
What alternatives have you tried?
No response
Does this feature request involve any updates to the reference design?
No
Implementation details
A CSS file should be generated when running npm run build.
The text was updated successfully, but these errors were encountered:
Summary
Many projects use Sass, but many do not. The cvi-styles package right now can only be consumed as a bunch of Sass files that assume presence of Sass as a dependency in an app that employs that library.
However this should not be mandatory since it could be perfectly fine to simply utilise CSS classes and CSS variables coming from the library. An app should be able to employ vanilla CSS, PostCSS, Less or something else and enjoy the CVI library at the same time.
Precompiled styles should be offered as one CSS file.
What alternatives have you tried?
No response
Does this feature request involve any updates to the reference design?
No
Implementation details
A CSS file should be generated when running
npm run build
.The text was updated successfully, but these errors were encountered: