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

@pixss/svelte

v1.2.2

Published

The Svelte UI component based on Pixss Css

Downloads

4

Readme

Svelte 3 Component Template

Known Vulnerabilities PRs Welcome

Table of Contents

  1. Features
  2. Getting started
  3. Developing
  4. Consuming components
  5. Backward Compatibility
  6. Preprocessors
  7. Testing
  8. Publishing to npm
  9. Frequently Asked Questions
  10. Credits & Inspiration

Features

  • Autoprefixing CSS
  • Preprocessing
  • Formating
  • Linting
  • Testing
  • Storybook

Getting Started

  1. Choose your template (regular/monorepo)

  2. Clone it with degit:

npx degit YogliB/svelte-component-template my-new-component
or
npx degit "YogliB/svelte-component-template#monorepo" my-new-component
  1. cd into the folder and install the node_modules:
cd my-new-component
git init
npm install

or:

yarn
  • For monorepo run:
npm run bootstrap

or:

yarn bootstrap
  1. Run npm init, to configure the project.

Your component's source code lives in src/components/[Footer].svelte.

Developing

  1. Start Rollup:
npm run dev
  1. Edit a component file in src/components, save it and watch the magic happens.

  2. Make sure your component is exported in src/components/index.js.

  3. Make sure your component is imported and nested in src/App.svelte, so you can preview and test it.

  4. Navigate to localhost:5000 to see your components live.

Consuming Components

Your package.json has a "svelte" field pointing to src/components/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").

Backward Compatibility

This template uses svelte-preprocess in order to integrate PostCSS auto-prefixing capabilities & Babel's transpiling capabilities into the build process.

Browserlist

PostCSS uses browserlist under the hood, in order to "know" what css to prefix.

The browserlist configuration is located inside the package.json.

Preprocessors

This template comes with the svelte-preprocess by default, which simplifies the use of preprocessors in components.

Usage

Getting Started with svelte-preprocess.

  • To configure svelte-preprocess use the sveltePreprocessConfig variable in ./preprocess.js

Testing

This template uses Cypress & testing-library for testing.

It is highly recommended going through their docs if you intend on testing your components.

You can witness a simple example by running npm run cy:open.

Frequently Asked Questions

What's the index.js file for?

It's for Svelte to be able to import multiple components from a single source.

For instance, it lets the user do:

import { Footer, MyOtherComponent } from 'my-component-library';

Instead of:

import Footer from 'my-component-library/components/Footer.svelte';
import MyOtherComponent from 'my-component-library/components/MyOtherComponent';

How do I include 3'rd party css in my components?

There are a few options to do this:

  1. Don't include 3'rd party css and just tell your users to do that (Probably using PostCSS).
  2. Include it via a cdn, like so:
@import url('https://unpkg.com/@scope/package/main.min.css');

Publishing to npm

Credits & Inspiration