Testing astro-critical-css

This commit is contained in:
Firq 2025-04-14 22:32:04 +02:00
parent 805ce53362
commit 120af666cb
Signed by: Firq
GPG key ID: DCE182BA39C697B2
4 changed files with 2319 additions and 116 deletions

View file

@ -1,8 +1,8 @@
import { defineConfig } from 'astro/config';
import mdx from "@astrojs/mdx";
import sitemap from "@astrojs/sitemap";
import criticalCss from 'astro-critical-css';
import astroMetaTags from "astro-meta-tags";
import { defineConfig } from 'astro/config';
// https://astro.build/config
export default defineConfig({
@ -11,5 +11,5 @@ export default defineConfig({
outDir: 'dist',
publicDir: 'public',
site: 'https://firq.dev/',
integrations: [sitemap(), mdx(), astroMetaTags()]
integrations: [sitemap(), mdx(), astroMetaTags(), criticalCss()]
});

2424
package-lock.json generated

File diff suppressed because it is too large Load diff

View file

@ -1,7 +1,7 @@
{
"name": "@firq/fgosite",
"type": "module",
"version": "0.2.0-pre.95",
"version": "0.2.0-pre.96",
"private": true,
"scripts": {
"dev": "astro dev",
@ -17,6 +17,7 @@
"@astrojs/sitemap": "^3.3.0",
"@fontsource-variable/work-sans": "^5.2.5",
"astro": "^5.6.1",
"astro-critical-css": "^0.0.7",
"astro-meta-tags": "^0.3.1",
"autoprefixer": "^10.4.21",
"iconoir": "^7.10.1",

View file

@ -232,6 +232,6 @@ export default async (): Promise<UserConfig> => {
After setting this whole thing up over the course of multiple months, with a variety of issues and shortcomings along the way, I hope that this is now ready for good.
I will, however, write a Forgejo Action for me to reuse in the future, as this would enable me to easily test other sites with the same concept.
If you want to check out the whole thing in action, check out <a href="https://forgejo.neshweb.net/Firq/firq-dev-website/src/branch/dev" target="_blank" rel="noopener noreferrer" >the website repository here </a>. In addition, you can find the reports that get generated <a href="unlighthouse.firq.dev" target="_blank" rel="noopener noreferrer" >here at unlighthouse.firq.dev</a>
If you want to check out the whole thing in action, check out <a href="https://forgejo.neshweb.net/Firq/firq-dev-website/src/branch/dev" target="_blank" rel="noopener noreferrer" >the website repository here </a>. In addition, you can find the reports that get generated <a href="https://unlighthouse.firq.dev" target="_blank" rel="noopener noreferrer" >here at unlighthouse.firq.dev</a>
Anyway, I wish I gave you an interesting insight in how Unlighthouse ensures good site quality - and how YOU can also profit from website testing in your CI.