-
Notifications
You must be signed in to change notification settings - Fork 21
Description
First and foremost, I'd like to thank you for an amazing package. We've been using it in production for some years already and it's just pure awesome.
Now, I've come by a situation where I thought some guidance might help greatly.
In our app, we've applied this type of pattern generously, where...
- Have some shared stylesheets, like
layout.m.css,button.m.cssortypography.m.css - Use
composesto compose my styles from those shared stylesheets, whether it was for components or pages, layouts etc.
This has worked wonderfully and has allowed me to define the basic bits and pieces of our styles in a reusable fashion. This way, if I have 5 different components that have some sort of inputs, all of the use compose to derive their basic apperance from those shared stylsheets. All good so far.
Now the problem:
I'm in the process of moving all our common components, like modal, title, button etc. to a Meteor package.
Is there an existing way of still sharing those common stylesheets across the app / package boundary, so that they could be used in both places?
My initial plan of action was to put the stylesheets in a dedicated directory outside of both app and package folders and then create symbolic links to both the app and package to be consumed by CSS Modules (we have a monorepo structure, but Git submodules could achieve the same effect).
Is there a better way, perhaps?
I already learned about sharing config between the app and package from this issue, but I didn't find anything about sharing stylesheets in any of the existing issues.
Once again, thanks for this package!