-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packages: Move build config to calypso-build package #30772
Conversation
I like the idea to publish the SCSS build scripts and configs as a standalone package. The common SCSS definitions (mixins, functions, variables) can live there. Also the PostCSS and webpack loader configs. The
The sources use a lot of SASS variables (all the |
Might be good to have a closer look at what we're actually depending on in blocks and if changing some Calypso variables/mixins to core equivalents makes more sense? |
Yep -- but in terms of moving forward, I'd play the transitivity card again: IIUC, a lot of these are based on a8c-color-studio, so it's unlikely that we can easily phase out our style basics altogether soon. We can however start depending on Gutenberg stuff and remove redundant definitions from ours. |
Thanks @jsnajdr , makes sense and confirms what I had vaguely in mind!
Not immediately relevant, but maybe it'd be possible to propagate some changes upstream (to color-studio)? I.e. have them change their SASS vars to CSS custom properties? (Not sure about the functions.) |
That could work: the
should be fairly easy. The question is whether the |
Seems like it has been brought up in that repo's issue tracker even: Automattic/color-studio#3 |
There are some other big bits that currently use SASS that are hard to replace with custom props:
|
Closing. This has served its purpose to inform pafL3P-kB-p2 and https://github.com/orgs/Automattic/projects/80. |
First steps. See p9oQ9f-87-p2 for context. Somewhat similar to WordPress/gutenberg#13814 -- ideally we'll converge at some point.
Jetpack counterpart PR: Automattic/jetpack#11344
Changes proposed in this Pull Request
TODO:
Tasks we'll need to do to follow through with this
assets/stylesheets/_shared
, which I'm currently directly including. Wondering if that should be its own package that thecalypso-builder
package can depend on. Est: 3dnode-sass
during build (and our files subsequently depend on the resultingpublic/custom-properties.css
). If we turn this into an npm, this would need to be part of the published package.__dirname
). Est: .5dconfig
. E.g. used for env, project name,... Hopefully avoidable or parametrizable. Est: 1dcomponents/jetpack-logo
lib/format-currency/currencies
lib/route/path
lib/simple-payments/constants
lib/simple-payments/utils
client/extensions
. Is any of that even still used? Can we yank it out altogether? (This is probably minor/optional)Testing instructions
See Automattic/jetpack#11344
/cc @Automattic/team-calypso @Automattic/gutenpack