Skip to content

Conversation

@elisechant
Copy link
Contributor

No description provided.


CSS is currently being distributed as minified and vendor-prefixed assets.

This is unnecessary since users (developing apps using npm) process styles for minification and vendor-prefixing, therefore css "as modules" should ship without being processed. This issue was raised by @liamfiddler [here](https://github.com/designsystemau/RFCs/pull/11#discussion_r724769922).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typically files from within the node_modules folders are not processed. That's the reason we publish transpiled babledfied js in our dists for react components. It's backwards and I agree it's not great but that's the norm these days. And one of the issues we have encountered in GOLD was that consumers were unable to use pancake because it included CSS files in their dist folders that were located within node_modules which most users were unable to write CSS loaders for their bundlers for one reason or another.


This is unnecessary since users (developing apps using npm) process styles for minification and vendor-prefixing, therefore css "as modules" should ship without being processed. This issue was raised by @liamfiddler [here](https://github.com/designsystemau/RFCs/pull/11#discussion_r724769922).

Where users want to consume full CSS however, they may still expect the asset to be vendor prefixed and minified. This scenario might be handled better by delivering styles from a CDN like [UNPKG](https://unpkg.com/).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So perhaps we leave both unprefixed and prefixed css files in with dist folder for consumers to choose from?

@elisechant elisechant mentioned this pull request Dec 14, 2021
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.

3 participants