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

marko-dynamic-tag

v1.0.0

Published

include marko components dynamically

Downloads

10

Readme

marko-dynamic-tag

Tag which allows dynamic loading of Marko v3 components

Usage

This tag is useful when you would otherwise have to loop over a large list of custom components. In that case you would typically need to check the name of each individual component, like so:

<for(c in data.components)>
    <component1 if(c.name === 'component1')/>
    <component2 else-if(c.name === 'component2')/>
    <component3 else-if(c.name === 'component3')/>
    ...
</for>

This verbosity can be reduced with dynamic-tag:

<for(c in data.components)>
    <dynamic-tag options=c.options model=c.model extra=c.extra/>
</for>

Caveats

  • w-id behavior is slightly different, see https://github.com/marko-js/marko-widgets/issues/49
  • w-* attributes aside from w-id, such as w-onchange, can not be used now
  • It is up to the caller of <dynamic-tag> to load the necessary dependencies for any template or widget that could be called. There may be cases where this is not possible, but we otherwise have no way to dynamically require files into a lasso bundle.

API

options

(required) Data used to find and load the component.

{
    path: string
    isWidget: boolean (optional)
    widgetId: string (optional)
}
path (required)

An absolute path to the component root. For a component located at src/components/component-name/, the path would be /path/to/project/root/src/components/component-name/. This is needed because <dynamic-tag> has no default context of where it was called from.

isWidget (optional, default: false)

Set widget to true to invoke the component as a widget.

widgetId (optional (default: '')

If widget is set to true, this will be the ID that the widget is invoked with, using w-id.

model

(optional) Primary data model that is passed to the component.

extra

(optional) Secondary data model that is passed to the component. It is temporary until we can pass an arbitrary number of data models without breaking existing usage.

Roadmap

  • Support arbitrary number of data models
  • Support Marko v4

License

Copyright (c) 2018 eBay Inc.

Use of this source code is governed by a MIT-style license that can be found in the LICENSE file or at https://opensource.org/licenses/MIT.