-
Notifications
You must be signed in to change notification settings - Fork 38
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
globs cant be fully replaced #41
Comments
Globs aren't meant to ever fully replaced, this is mentioned in the readme:
I do agree that the hard coded |
am not sure what this part means
still i can make a PR with a check for globs & if empty then fallback to this.options.globs.push(
...flatMap(this.options.folders, folder => {
return this.options.extensions.map(extension =>
rootPath(`${folder}/**/*.${extension}`)
);
})
); |
https://github.com/FullHuman/purgecss-webpack-plugin#paths
|
oh okay, so which PR do u prefer ?
|
Feel free to send a PR that improves the docs regarding |
according to
https://github.com/spatie/laravel-mix-purgecss/blame/master/README.md#L92-L93
adding
should replace the package defaults, but because of
laravel-mix-purgecss/src/index.js
Lines 32 to 39 in c48b793
this is not possible and you are basically adding an extra entry point to be scanned.
also https://github.com/spatie/laravel-mix-purgecss#usage-outside-of-laravel is not true because if
root/app/
is not found you will get an error.to test
globs
optionconsole.log(JSON.stringify(globs, null, 1));
to https://github.com/spatie/laravel-mix-purgecss/blob/master/src/createPurgeCssPlugin.jsnpm run dev/watch
and check the consolebtw globs extension could be omitted https://github.com/FullHuman/purgecss-webpack-plugin/blame/master/README.md#L68 as purgecss will use the extensions option to fill it.
The text was updated successfully, but these errors were encountered: