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

@douganderson444/svelte-component-gateway

v0.0.19

Published

Grabs a compiled Svelte component (ES Module) from the interwebs and mounts it so it to the DOM, so you can check it out, use it, and run your data (props) through it.

Downloads

7

Readme

Svelte Component Gateway

Grabs a compiled Svelte component (ES Module) from the interwebs and mounts it so it to the DOM, so you can check it out, use it, and run your data (props) through it.

Usage

Save a Svelte component to the internet (maybe using something like Web3 Repl Deploy) then paste the URL for the resulting es module / Svelte Component into this gateway.

This gateway will render the component and add the props so you can check it out.

TODO

  • [x] Pass in props in a variable way
  • [x] Pass props back to parent (to save them)
  • [x] Pass default props to parent to capture schema

iFrame TODO

  • [x] Sandbox the iframe for untrusted code execution
  • [x] Prevent fetch
  • [x] Prevent XMLHttpRequest
  • [x] Prevent WebSocket
  • [x] Prevent EventSource
  • [ ] Prevent adding iframes to the iframe
  • [ ] Prevent href anchors with searchParams
  • [ ] Prevent sanitize props as JSON objects only

API

Use the Gateway in your mini-apps:

Using Svelte to generate a CustomEvent

<script>
	import { Gateway } from '@douganderson444/svelte-component-gateway';

	// props
	export let count = 0;

	function handleChange(event) {
		console.log(`The count is now: `, event.detail.count);
	}
</script>

// YourApp.svelte

<Gateway
	esModule={ContactCard}
	props={{ firstName: 'Doug', lastname: 'Anderson' }}
	on:change={handleChange}
/>

Using Vanilla JS (see ref)

// yourscript.js

import { Gateway } from 'svelte-component-gateway'

// fetch your esModule from the interwebs, [IPFS](https://docs.ipfs.io/concepts/ipfs-gateway/), or perhaps [Arweave](https://docs.arweave.org/developers/server/http-api)
const fetched = await fetch(url);
const ExampleComponent = await fetched.text();

const gateway = new Gateway({
    target: document.getElementById('gateway-element'),
	props: {
		esModule: ExampleComponent,
        // optional props
		// assuming ExampleComponent.svelte contains something like
		// `export let answer`:
        props: { answer: 42 } // we want the answer to be 42 instead of the default
})

gateway.$on('change',
    event => {
        // save them somewhere
        // defaults props will be emited on load
        console.log("The following properties changed: ", event.detail)
        }
)


...
<!-- in your html: -->

<div id='gateway-element'></div>