Excluding PurgeCSS content by folder names?

[nsnyder]

Hello, I'm working on an app and trying to cut back my CSS size as much as possible.

I have this sort of file structure:

/resources/admin/...
/resources/frontend/...
/resources/generic/...
/resources/poorly-organized-component/...
/resources/components/admin/component-one/...
/resources/components/frontend/component-two/...
etc.

Currently, I'm building an admin.css file and a frontend.css file. I'd like to figure out how to set content up for PurgeCSS such that it doesn't check anything in an "admin" folder when building frontend.css and doesn't check anything in a "frontend" folder when building admin.css.

Effectively, admin.css should be purging based on the contents of:

/resources/admin/...
/resources/generic/...
/resources/poorly-organized-component/...
/resources/components/admin/component-one/...

And frontend.css should be purging based on the contents of:

/resources/frontend/...
/resources/generic/...
/resources/poorly-organized-component/...
/resources/components/frontend/component-two/...

I'm currently using the laravel-mix-purgecss package, and I think I've figured out how to build these two configurations separately, however, I'm having trouble with the content setup for PurgeCSS.

This is what I'm currently trying for the admin.css file:

adminCssMixer.purgeCss({
    content: [
        "app/**/!(frontend)/*.php",
        "resources/**/!(frontend)/*.html",
        "resources/**/!(frontend)/*.js",
        "resources/**/!(frontend)/*.jsx",
        "resources/**/!(frontend)/*.ts",
        "resources/**/!(frontend)/*.tsx",
        "resources/**/!(frontend)/*.php",
        "resources/**/!(frontend)/*.vue",
    ]
});

However, it doesn't seem to be having any effect. The file size is exactly the same, even though I have distinct admin styles that aren't used on the frontend. Can anyone see what I'm doing wrong or point me in the right direction? I'm fairly new to Linux globbing, so maybe I'm just not setting things up correctly.

Thanks!
nsnyder

[nsnyder]

I did not find a good solution for this, unfortunately. I've opted to use the content for both the frontend and backend for all CSS files, so some of them are likely larger than necessary, but I think that the upsides outweigh the downsides for us.