JSPM

astro-beasties

0.0.1
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 40
  • Score
    100M100P100Q54847F
  • License SEE LICENSE IN LICENSE

Inline 🦔

Package Exports

  • astro-beasties
  • astro-beasties/Target/Function/Integration.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (astro-beasties) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Astro

Related

Build
Dependency
Version
Star
Download
Compress 🗜️
Build
Dependency
Version
Star
Download
Format 🗻

Inline 🦔

This Astro integration brings beasties to your Astro project.

Beasties is a plugin that inlines your app's critical CSS and lazy-loads the rest.

Note

Inline will not inline your requests, only your statically generated build and pre-rendered routes.

Installation 🚀

There are two ways to add integrations to your project. Let's try the most convenient option first!

astro add command

Astro includes a CLI tool for adding first party integrations: astro add. This command will:

  1. (Optionally) Install all necessary dependencies and peer dependencies
  2. (Also optionally) Update your astro.config.* file to apply this integration

To install Inline, run the following from your project directory and follow the prompts:

Using NPM:

npx astro add astro-beasties

Using Yarn:

yarn astro add astro-beasties

Using PNPM:

pnpx astro add astro-beasties

Install dependencies manually

First, install the Inline integration like so:

npm install -D -E astro-beasties

Then, apply this integration to your astro.config.* file using the integrations property:

export default {
    integrations: [(await import("astro-beasties")).default()],
};

Getting started

Beasties will now automatically inline the critical CSS of your HTML files.

Default Inlining

You can override any of the default options from the configuration of:

or disable them entirely:

export default {
    integrations: [
        (await import("astro-beasties")).default({
            Beasties: false,
        }),
    ],
};

Add Multiple Paths

You can add multiple paths to inline by specifying an array as the Path variable.

astro.config.ts

export default {
    integrations: [
        (await import("astro-beasties")).default({
            Path: ["./Target", "./Build"],
        }),
    ],
};

Input-Output Mapping

You can also provide a map of paths for different input output directories.

astro.config.ts

export default {
    integrations: [
        (await import("astro-beasties")).default({
            Path: new Map([["./Source", "./Target"]]),
        }),
    ],
};

Or an array of the two.

astro.config.ts

export default {
    integrations: [
        (await import("astro-beasties")).default({
            Path: [
                // Inline Target
                "./Target",
                // Inline Target one more time into a different directory
                new Map([["./Target", "./TargetInline"]]),
            ],
        }),
    ],
};

File Filtering

You can filter files to exclude specific ones from inlining. A filter can be an array of regular expressions or a single match. You can also use functions to match on file names:

astro.config.ts

export default {
    integrations: [
        (await import("astro-beasties")).default({
            Exclude: [
                "File.html",
                (File: string) => File === "./Target/index.html",
            ],
        }),
    ],
};

Controlling Logging

You can control the logging level by setting the Logger parameter. The default value is 2, but you can set it to 0 if you don't want to see debug messages:

export default {
    integrations: [
        (await import("astro-beasties")).default({
            Logger: 0,
        }),
    ],
};

Changelog

See CHANGELOG.md for a history of changes to this integration.