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

sandeep49g-web-component1-demo

v1.0.50

Published

My webpack project

Downloads

6

Readme

🚀 Web Component Demo

This project has been created using webpack-cli, you can now run

npm run build

or

yarn build

to bundle your application

Ways to share styles with web component:

  1. CSS variables Pros: We can have default css property inside web component Cons: Lot of CSS properties need to provide individually, can be time consuming

  2. ::part(some-box) // some-box is part name in template of web component For Ex: In user-card web component: some box In consumer CSS: user-card::part(some-box) {...} Pros: We can have default css properties for whole group We can have lot of CSS properties together in single group, much better than first approach (CSS variables)

  3. slot tag in web component, we can style from outside for that slot (Slot is not a part of shadow root if template is coming from outside, default template of slot will bepart of shadow root) For Ex: In user-card web component: and CSS: ::slotted(div.slot-email) {...} In consumer: [email protected] In consumer CSS: .slot-email {...} Note: ::slotted doesn't work for internal template, we can provide normal css with css selectors for default template Pros: (If there is no default template inside web component)

    1. We can have default css for slot template which is coming from outside.
    2. We can also override css for slot template which is coming from outside. Cons: (If there is a default template inside web component)
    3. We can't override css for default template of slot which is written inside web component
  4. ::shadow, almost like ::part For Ex: In consumer CSS: usercard::shadow .user-card img { width: 10%; } Cons: Very less support of browsers, doesn't work mostly

  5. @apply CSS variables group For Ex: @apply --typography Cons: Very less support of browsers, doesn't work mostly