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
docs: update in readme the list of plugins and loaders #15996
Conversation
…discus/pug-loader`
For maintainers only:
|
@webdiscus Thanks for your update. I labeled the Pull Request so reviewers will review it again. @alexander-akait Please review the new changes. |
@alexander-akait |
@alexander-akait |
Hi @webdiscus. Just a little hint from a friendly bot about the best practice when submitting pull requests:
You don't have to change it for this PR, just make sure to follow this hint the next time you submit a PR. |
Just ingore random CI errors |
Thanks |
Motivation
In README.md are added
pug-plugin
and modern powerfulpug-loader
.pug-plugin
This plugin enable to define Pug files in Webpack entry, extracts JS and CSS from sources specified directly in Pug:
All source scripts and styles can be required in Pug, e.g.:
Generated HTML contains hashed CSS and JS output filenames:
This plugin make much easy the usage Pug with Webpack.
Test coverage > 99%.
@webdiscus/pug-loader
The original pugjs/pug-loader has problems:
npm i pug-loader --force
The alternative
@webdiscus/pug-loader
can do absolutely everything thatpugjs/pug-loader
can (100% compatible with pugjs/pug-loader), plus:Suggestion
Instead of
install size
displaypublish size
of a package.E.g. the pug-plugin have
public size
only 100 KB, butinstall size
is 8 MB, becase containsdocs
with many resources, has much tests with real files to test: images, fonts, etc.What kind of change does this PR introduce?
docs: update readme
Did you add tests for your changes?
tests are not needs for readme
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
Nothing