danielroe / danielroe/beasties

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

Open
#147 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
TypeScript
Stars
699
Forks
25
Avg merge
20h 13m
Merged PRs (30d)
35

Description

### 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**](https://github.com/danielroe/beasties#properties) as command-line arguments. Example command:

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

But Beasties unfortunately haven’t command-line interface.

1. Critical has the [**Grunt plugin**](https://github.com/bezoerb/grunt-critical). I run Critical for all HTML files of my site use [**Grunt files object**](https://gruntjs.com/configuring-tasks#building-the-files-object-dynamically):

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

But Beasties unfortunately haven’t a Grunt plugin.

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

Thanks.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.