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 🙏

© 2024 – Pkg Stats / Ryan Hefner

svelte-adapter-browser-extension

v1.0.1

Published

![NPM Version](https://img.shields.io/npm/v/svelte-adapter-browser-extension) ![Libraries.io dependency status for latest release](https://img.shields.io/librariesio/release/npm/sveltekit-adapter-chrome-extension)

Downloads

5

Readme

svelte-adapter-browser-extension

NPM Version Libraries.io dependency status for latest release

forked from michmich112/sveltekit-adapter-chrome-extension

This project is a fork from the repository mentioned above. The goal is:

  • Fix compatibility issues with SvelteKit v2.
  • Improve development/publishing.
  • Make it ready for improvements/features (e.g.: more compatibility with other browsers, more updated dependencies, more config options, etc.)

Description

Adapter for SvelteKit apps that prerenders your site as a collection of static files and removes inline scripts to comply with content source policies of Chrome extensions using manifest v3.

Based on @sveltekit/adapter-static. Credit goes to these people for their hard work to make Svelte so great

🚧 If you are using SvelteKit v1.0.0+, make sure to set your prerender=true for every page reference by your extension so SvelteKit generates the HTML files. (c.f. Issue #27)

Usage

Install with npm i -D svelte-adapter-browser-extension, then add the adapter to your svelte.config.js:

// svelte.config.js
import adapter from "svelte-adapter-browser-extension";

export default {
  kit: {
    adapter: adapter({
      // default options are shown
      pages: "build",
      assets: "build",
      fallback: null,
      precompress: false,
      manifest: "manifest.json",
    }),
    appDir: "app",
  },
};

Options

pages

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

assets

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

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

precompress

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

manifest

Specify manifest file name if you want different manifests for different target platforms, e.g. chrome_manifest.json, firefox_manifest.json. This file name must match one that is present in the static directory (the dir containing your static files). The selected target file will be renamed to manifest.json in the build directory, and all other .json files with manifest in the name won't be copied.

License

MIT