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-dynamic-import

v2.0.0

Published

Let your CMS decide which components to import.

Downloads

3,893

Readme

astro-dynamic-import 🌊

This Astro integration lets you import components dynamically, allowing you to pick and choose which components add their scripts and styles to the page. Now you can let a CMS or DB query decide your components without astro sending JS and CSS for all of them!

Why Import Dynamically?

Astro decides which scripts and styles get included on the page based on the import statements alone. If different components are picked based on the request, this heuristic quickly results in too many assets being sent to the browser. Importing dynamically lets you import components based on a condition and only the rendered components will send their associated assets to the browser.

Installation

Manual Install

First, install the astro-dynamic-import package using your package manager. If you're using npm or aren't sure, run this in the terminal:

npm install astro-dynamic-import

Next, apply this integration to your astro.config.* file using the integrations property:

  // astro.config.mjs
  import { defineConfig } from 'astro/config';
+ import dynamicImport from 'astro-dynamic-import';

  export default defineConfig({
    // ...
    integrations: [dynamicImport()],
    //             ^^^^^^^^^^^^^
  });

Usage

Once the integration is installed and added to the configuration file, you can import the default function from the "astro:import" namespace.

---
import dynamic from "astro:import"
const toImport = random() ? "components/Counter.astro" : "components/Ticker.astro"
const Component = await dynamic(toImport)
const initial = 3
---
<Component {initial} />

The dynamic function takes the path to a component relative to your source directory ("/src" by default). It returns a promise that resolves to the astro component.

Note that only .astro components can be imported. The components must be located in the src/components folder. The imported component must be used in an .astro file located within src/pages due to reasons explained here.

Troubleshooting

For help, check out the Discussions tab on the GitHub repo.

Contributing

This package is maintained by lilnasy independently from Astro. The integration code is located at packages/dynamic-import/integration.ts. You're welcome to contribute by opening a PR or submitting an issue!

Changelog

See CHANGELOG.md for a history of changes to this integration.