Automattic / Automattic/jetpack
Enhancement: assess removal of postcss from search package
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
### Impacted plugin
Jetpack
### What
Assess removal of postcss from search package
### How
> https://github.com/postcss/postcss-custom-properties#preserve
https://github.com/Automattic/jetpack/blob/46db58bbc8358b304b152c4ed849909b1f8d6086/projects/packages/search/postcss.config.js#L8
https://github.com/Automattic/jetpack/blob/46db58bbc8358b304b152c4ed849909b1f8d6086/projects/packages/search/tools/webpack.instant.config.js#L101
We currently have some issues compiling CSS variables into target file when using the postcss processor, so we removed postcss for the dashboard. We want to assess whether we could remove it all from the search package.
Contributor guide
Research direction
Read projects/packages/search/postcss.config.js and projects/packages/search/tools/webpack.instant.config.js, especially the linked lines. Check how the search package currently compiles CSS variables and compare this with the dashboard's removal of postcss. Done means documenting whether postcss can be removed from the search package without breaking the target CSS output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100