gajus/babel-plugin-react-css-modules

Feature: make postcss configurable

Open

#83 opened on 2017年5月5日

GitHub で見る
 (2 comments) (2 reactions) (0 assignees)JavaScript (2,044 stars) (176 forks)batch import
enhancementhelp wanted

説明

I like to use postcss to transform css with certain plugins, and wouldn't want to have to give this up in order to use this plugin. Luckily, it already uses postcss, so it should be pretty trivial to expose an option to process with additional postcss plugins if needed. I'd be happy to pull request this in, just wanted to open this issue to bring it up and see if maintainers had any thoughts!

コントリビューターガイド

技術スタック
javascriptnodejscss
領域
frontendtooling
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
1
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
under 1 hour
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Basic understanding of Babel pluginsFamiliarity with PostCSS
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
70
調査方針
The issue requests adding an option to the Babel plugin to allow users to pass additional PostCSS plugins. Since the plugin already uses PostCSS internally (likely in the CSS module resolution process), the implementation would involve modifying the plugin's options schema (e.g., in the main plugin function) and passing the user provided plugins to the PostCSS pipeline. The source files are likely in the `src/` directory. Look for where PostCSS is invoked (e.g., using `postcss` npm package) and add a new option (e.g., `postcssPlugins`) that is an array of PostCSS plugins to apply after or alongside the default transformations. The change is small and localized, making it ideal for a first contribution.
Feature: make postcss configurable · gajus/babel-plugin-react-css-modules#83 | Good First Issue