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 was archived by the owner on Dec 28, 2024. It is now read-only.
The main attribute on package.json resolves the import currently via main: src/main/css/index.css. The postcss-import plugin can also import sub modules with import statements like this:
Ideally the main attribute could be set to a directory like src/main/css (With functionality similar to the <base> html element) and this would be the base directory for all module imports. The above statement could then be shortened to:
Does postcss-partial-import support this? Would this project be interested in supporting it? Here's a link to the original uncss issue that made this important: Uncss causes infinite loop
I'm publishing pure css modules like these:
The
mainattribute onpackage.jsonresolves the import currently viamain: src/main/css/index.css. Thepostcss-importplugin can also import sub modules with import statements like this:Ideally the main attribute could be set to a directory like
src/main/css(With functionality similar to the<base>html element) and this would be the base directory for all module imports. The above statement could then be shortened to:So in other words if we want the entire kitchen sink (
index.css) then we do:But if we only want
faucet.cssor perhaps just a washer that goes to the faucet then we do:or
Does postcss-partial-import support this? Would this project be interested in supporting it? Here's a link to the original
uncssissue that made this important:Uncss causes infinite loop