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

eleventy-plugin-copy-local-assets

v1.0.1

Published

Set up a dynamic passthrough copy in Eleventy for a folder holding both the content file and the assets used on the page.

Downloads

6

Readme

eleventy-plugin-copy-local-assets

Set up a dynamic passthrough copy in Eleventy for a folder holding both the content file and the assets used on the page.

When do I need this?

This allows you to save a page's assets within the same folder as the content itself. For example, imagine a special page within a folder:

.
+-- /sample
|   +-- /index.md (Content file)
|   +-- /diamond.svg (Asset file)

Instead of reaching for a filter to resolve the URL to your common assets folder, this "one-off" asset is accessible within the same folder, so you are able to find it with ./ and no other processing. This means you don't need to manually edit your Eleventy configuration file to passthrough your assets from that folder — it is all dynamically handled by the plugin.

Define a copyLocalAssets entry with a glob string or a true boolean in your frontmatter, and that's it.

Usage

Install the package from NPM:

npm install eleventy-plugin-copy-local-assets

Then, include it in your .eleventy.js config file:

const copyLocalAssets = require("eleventy-plugin-copy-local-assets");

module.exports = (eleventyConfig) => {
	eleventyConfig.addPlugin(copyLocalAssets, { verbose: false });
};

Frontmatter examples

---
title: Boolean Example
copyLocalAssets: true
---
---
title: glob + Permalink Example
permalink: /sample/working-example/index.html
copyLocalAssets: '*.svg'
---

Note: You can rewrite the permalink and the assets will be in the same folder as the content file.

Config options

| Option | Type | Default | | --------- | ------- | ------- | | verbose | boolean | false |

When the verbose option is set to true, the console will log each file it finds with a truthy filesToCopy and report the input file, output file, and the number of files matching the provided glob.

Credits

Contributors