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

rollup-plugin-lit-html-style

v0.3.3

Published

rollup plugin for extracting style and embed into lit html

Downloads

36

Readme

rollup-plugin-html-style

Published on npm

Changes in 3.0

  • node-sass has been replaced with sass

Changes in 2.0

exported template is no longer TemplateResult but CSSResult. if fore some rease you need to inject style directly into template, use unsafehtml or provide your own tempplate

  • all local scss imports must start with relative path! (otherwise resolved to node_module)
  • files are resolved from processed.cwd (might enchance when time)
  • resolving can be overridden by compilerOptions (@see node-sass)

Example

test.js

import {LitElement,html,customElement} from 'lit-element';
import style from './test.scss';

@customElement('test-element')
export class Test extends LitElement{
  static styles = [style]
  render(){
    return html`<p>test</p>`;
  }
}

test.scss

:host{
  display: inline-block;
  background: red;
}

rollup.config.js

import babel from "rollup-plugin-babel";
import preset from "@babel/preset-env";
import style from 'rollup-plugin-lit-html-style';

const esmodules = true;

export const config = {
 input: 'test.js',
 output: { file: 'demo.js' }
  plugins: [
   style({ esmodules }),
   babel({
    // include .scss, might need to transpile the es6 template result
    extensions = [".js", ".scss"],
    presets: [[preset, { targets: { esmodules } }]]
   })
 ]
}

export default config;

Options

required

none

optional

esmodules?:boolean default: true

include?:string[] default: ['**/*.scss']

exclude?:string[] default: []

compress?:boolean default: true

env?:string default: esBrowsers|'defaults'

if option.esmodules the plugin makes a lookup at caniuse-api for browsers that supports es6-module, else env is default @BroswerList

template?:(css: string) => string

(css) => `
  import { html } from "lit-element";
  export const style = html\`<style>${css}</style>\`;
  export default style;
`;

compiler?:({ file, data, ...options }) => Promise<{data}>

BringYourOwnCompiler - atm only node-sass is bundled, but provide your own or leave a feature request for other compilers or features?!

import nodeSass from "node-sass";
export default (options) =>
  new Promise((resolve, reject) => {
    const resolved = ({ css }) => resolve({ data: css.toString() });
    nodeSass.render(options, (err, res) => (err ? reject(err) : resolved(res)));
  });

processor?:({ file, data }) => Promise<string>

BringYourOwnProcessor - this plugin uses postcss with postcss-preset-env for autoprefix and cssnano for compress

import postcss from "postcss";
export default (options) => {
  const { file, data, plugins } = options;
  return new Promise((resolve, reject) => {
    postcss(plugins)
      .process(data, { from: file })
      .then(({ css }) => resolve(css), reject);
  });
};