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

astro-public

v0.1.0

Published

Add custom 'public' directories in Astro

Downloads

261

Readme

astro-public

npm version readme

Add custom "public" directories for static assets in Astro

Why?

  1. Serve static assets from anywhere, including packages
  2. Have multiple static asset directories instead of only the default public directory
  3. Provide placeholder assets that can be overwritten by assets in Astro's public directory

Examples

Use as an Integration

// astro.config.mjs
import { defineConfig } from 'astro/config';
import publicDir from 'astro-public';

export default defineConfig({
  // Creates a 'public' directory at '/static'
  integrations: [publicDir('static')],
});

Use Inside an Integration

// package/index.ts
import type { AstroIntegration } from "astro";
import { addIntegration } from "astro-integration-kit";
import publicDir from "astro-public";

export default function myIntegration(): AstroIntegration {
    return {
        name: "my-integration",
        hooks: {
            "astro:config:setup": ({
                updateConfig,
                config,
                logger,
            }) => {

                // Creates a 'public' directory at '/package/static'
                addIntegration({
                    integration: publicDir({
                      dir: "static",
                      cwd: import.meta.url
                    }),
                    updateConfig,
                    config,
                    logger,
                })

            }
        }
    }
}

Adding multiple directories

// Creates a 'public' folder at '/static', and '/assets'
publicDir(
  'static',
  'assets'
)

Using custom cwd

// Creates a 'public' folder at 'src/static'
publicDir(
  {
    cwd: 'src'
    dir: 'static'
  }
)

Change when assets get copied

// Assets will be copied before the build is generated
publicDir(
  {
    dir: 'static'
    copy: 'before'
  }
)

Debug logging

// Log all debug messages
publicDir(
  {
    dir: 'static'
    log: 'verbose'
  }
)

Option Reference

dir

Type: string

Path to custom 'public' directory, relative paths are resolved relative to cwd

cwd

Type: string

Default: root

Path to base directory, used to resolve relative dir paths. For this property, relative paths are resolved relative to the project root

copy

Type: "before" | "after"

Default: "before"

When to copy directory into build output

  • before: Assets are copied to build output before the build starts, assets can be overwrriten by assets located in /public
  • after: Assets are copied to build output after the build finished, assets will overwrrite assets located in /public

log

Type: boolean | "verbose"

Default: false

If truthy, logs a message when copying custom 'public' directory to build output

If verbose, logs a message if dev middleware finds a static asset inside the custom 'public' directory