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

drupal_svelte_component_menu

v1.0.2

Published

Svelte menu component for decoupled applications.

Downloads

1

Readme

Drupal svelte component menu

TODO

  • [ ] Publish to npm to make it easier to consume component.
  • [ ] Test component
  • [ ] Auto Publish to npm
  • [ ] Storybook Integration
  • [ ] Initialize component using url
  • [ ] Add example to consume component outside svelte (should be possible after the module is published to npm).

Setting up

  • Run npm init (or yarn init)

Available tasks.

Refer to available tasks inside package.json "scripts" for latest.

  • yarn run build to build the component
  • yarn run autobuild to build the component while developing, to build continusly upon source code update.
  • yarn run dev to start a local development server for testing and as well as run autobuild.
  • yarn start to serve example.
  • yarn start --dev to serve example in dev mode.

Example

Running yarn start should start a local server. The link to view the example should be available in command line output and should look something like http://localhost:5000. Please note that, in case port 5000 is already busy, it may pick up some other random port and the link would look similar to http://localhost:57391.

Consuming components

Your package.json has a "svelte" field pointing to src/index.js, which allows Svelte apps to import the source code directly, if they are using a bundler plugin like rollup-plugin-svelte or svelte-loader (where resolve.mainFields in your webpack config includes "svelte"). This is recommended.

For everyone else, npm run build will bundle your component's source code into a plain JavaScript module (dist/index.mjs) and a UMD script (dist/index.js).