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
{{ message }}
This repository has been archived by the owner on Jul 30, 2022. It is now read-only.
In the monorepo, everything is a package. So, I would recommend placing Sass mixins to a separate package, which could be marked as "private": true in case there is nothing to publish to npm.
See for example how mwc-button web component imports SCSS for icon from the other package.
that needs to be compiled and included in /packages/app2/src/index.js
There is no components for them as all components are in /components.
Is it safe to say that the structure you have built is only for this specific /packages/* setup? The aybolit idea is to be something like Vaadin but much more easily extendable as seen in /core where the base has been set and all other packages extend it.
With aybolit setup, where should I include scss mixins/variables that are being used throughout multiple packages?
Before I used
sass-resources-loader
in webpack to load the mixins to all scss included.The text was updated successfully, but these errors were encountered: