Skip to content

Conversation

@nathanleclaire
Copy link
Contributor

@nathanleclaire nathanleclaire commented Jul 19, 2022

Closes #269

If we can find another way to tamp down the logspam, I might be open to keeping it, but @bluskript I'd need you to please elaborate on the advantages. We have SCSS going already, and it seems to serve a lot of the same purposes. (and @apply seems to confuse SCSS, so I'm not sure I want to write a "different type" of CSS in the JS than in our preprocessed stuff)

Generally, I'm thinking I want to remove it and keep doing things the old fashioned way cause it's simpler to understand. Appreciate the effort to try something new though.

I think this PR still doesn't look exactly right so it's a WIP. @bluskript what am I missing?

e.g., this PR:

Screen Shot 2022-07-19 at 11 40 56 AM

main:

Screen Shot 2022-07-19 at 11 41 55 AM

@nathanleclaire nathanleclaire requested a review from bluskript July 19, 2022 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

inline-css-modules sourcemap message spam in CI logs

2 participants