npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

sveltekit-adapter-html-like

v1.0.1

Published

SvelteKit adapter for HTML-like template engines such as PHP, Blade, Handlebars, etc.

Readme

sveltekit-adapter-html-like

License Version Build

Adapter for SvelteKit apps that prerenders your site as static files for template engines such as PHP, Blade, Embedded Ruby (ERB), Handlebars, EJS etc.

This package is a fork of @sveltejs/adapter-static (currently tracking v3.0.10) that adds a couple of extra features:

  • tag injection
  • string replacement
  • minify/prettify output
  • custom file extensions

Requires SvelteKit 2 and Node 20.19, 22.13 or 24 and later.

Usage

Install with npm i -D sveltekit-adapter-html-like, then add the adapter to your svelte.config.js:

// svelte.config.js
import adapter from 'sveltekit-adapter-html-like';

export default {
	kit: {
		adapter: adapter()
	}
};

Unless you're in SPA mode, every route must be prerenderable. The usual way to achieve this is to add export const prerender = true to your root +layout.js.

Options

pages

Type: string
Default: build

The directory to write prerendered pages to. It defaults to build.

assets

Type: string
Default: the value of pages

The directory to write static assets (the contents of static, plus client-side JS and CSS generated by SvelteKit) to. Ordinarily this should be the same as pages, and it will default to whatever the value of pages is, but in rare circumstances you might need to output pages and assets to separate locations.

fallback

Type: string
Default: undefined

Specify a fallback page for SPA mode, e.g. index.html or 200.html or 404.html.

precompress

Type: boolean
Default: false

If true, precompresses files with brotli and gzip. This will generate .br and .gz files.

Compression runs after the markup has been transformed, so the compressed copies match what the adapter actually writes. Note that SvelteKit only compresses a fixed set of extensions (.html, .js, .css, .json, .svg, .xml, .wasm, .txt, .md, .mdx), so setting a targetExtension such as .php leaves your pages uncompressed — which is usually what you want, since the server executes those rather than serving them as-is. Assets are compressed either way.

injectTo

Type: object
Default: {}

Allows the injection of markup, valid HTML or otherwise, into the <head> or <body>. You can use the same positions as insertAdjacentHTML:

  • beforebegin
  • afterbegin
  • beforeend
  • afterend

Example

Let's inject some WordPress tags into the page

adapter({
	injectTo: {
		head: {
			beforeend: ['<?php wp_head(); ?>']
		},
		body: {
			beforeend: ['<?php wp_footer(); ?>']
		}
	},
	targetExtension: '.php'
});

replace

Type: array
Default: []

String replacements run on every page

Example

Once again, a WordPress example

adapter({
	replace: [
		{
			from: '<html lang="en">',
			to: '<html <?php language_attributes(); ?>>'
			// many: true (optional)
		}
	],
	targetExtension: '.php'
});

minify

Type: boolean
Default: false

Enable minification of output files. Takes precedence over prettify.

prettify

Type: boolean
Default: true

Format the output with Prettier. Your project's Prettier config is picked up automatically, if there is one. Ignored when minify is enabled.

strict

Type: boolean
Default: true

Fail the build when routes are not prerenderable. See the adapter-static docs.

targetExtension

Type: string
Default: .html

Modifies the extension of the target file, e.g. .php or .hbs

SPA mode

You can use sveltekit-adapter-html-like to create a single-page app or SPA by specifying a fallback page.

In most situations this is not recommended: it harms SEO, tends to slow down perceived performance, and makes your app inaccessible to users if JavaScript fails or is disabled (which happens more often than you probably think).

The fallback page is a blank HTML page that loads your SvelteKit app and navigates to the correct route. For example Surge, a static web host, lets you add a 200.html file that will handle any requests that don't otherwise match. We can create that file like so:

// svelte.config.js
import adapter from 'sveltekit-adapter-html-like';

export default {
	kit: {
		adapter: adapter({
			fallback: '200.html'
		})
	}
};

When operating in SPA mode, only pages that have the prerender option set will be prerendered.

Related

License

This work is licensed under The MIT License