question(documentation): how to run Beasties recursively for all HTML files of the project?

Open Beginner friendly
#147 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
vite, webpack
Domain
cli, documentation

Research direction

Start with the Beasties documentation and its linked properties reference, then check how the existing Vite and Webpack integrations expose Beasties. Document whether users can process a glob of HTML files without those integrations, including the supported workflow and configuration; if no such workflow exists, make that limitation explicit.

Written by the indexing model from the issue text.

Description

enhancement
1. Summary

It would be nice if Beasties documentation will contain information how users that not use Vite and Webpack can run Beasties for all HTML files of the project.

For example, I have a static site with HTML files. Glob template for my HTML files is output/**/*.html. What I need to do to running Beasties for all HTML files of my static site?

2. Not helped

  1. It would be nice if Beasties will have command-line interface with supporting glob templates and passing Beasties properties as command-line arguments. Example command:

    beasties --noscriptFallback --src "output/**/*.html"

    But Beasties unfortunately haven’t command-line interface.

  2. Critical has the Grunt plugin. I run Critical for all HTML files of my site use Grunt files object:

    files: [
	cwd: "."
	dest: "."
	expand: true
	src: ["output/**/*.html"]
]

    But Beasties unfortunately haven’t a Grunt plugin.

  3. I can’t find answers to my question in Beasties and Critters repositories.

Thanks.

Dominant language
TypeScript
Stars
700
Forks
25
Avg merge
20h 13m
Merged PRs (30d)
35

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from danielroe/beasties

All issues in danielroe/beasties

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.