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

gwi-theming

v1.0.0

Published

Enables theming within a project. This module establishes theme inheritance for FrontendComponents.

Downloads

5

Readme

Installation

  1. After installing, copy and rename config.theme.example to your root project folder as config.theme.
  2. Adjust the values for the variables inside config.theme if necessary. Especially make sure that you:
  • declare only the elements, components and pages that you will actually use
  • adjust the path for @publicThemeFolder and @projectThemeFolder if necessary
  • have the Themes that you declare installed

Make a FrontendComponent themable

  1. Inside a FrontendComponent's stylesheet, you import the config.theme as follows:
// modal.less

// specify the type of your FrontendComponent
// Can take one of the following values: element, component, page
@type : 'component';

// A unique identifier for this stylesheet.
// This is the identifier that will be used by `config.theme` to set the theme,
// as well as by the theme.less file to locate the theme variable files inside the theme packages.
@name : 'modal';

@import (multiple) 'config.theme';
Where `@type` can be one of the following values from the: `element`, `component`, `page`.
And `@name` is a unique identifier for the stylesheet. You will later on set the theme for that unique identifier in the `config.theme`
  1. Then, inside your config.theme file, you declare which Theme to use for which element, component or page:

    // config.theme
    
    @modal : 'gwi-theme-common';
  2. Now make sure that every LESS variable that you use inside your modal.less component, is at least declared in

  • the Common Theme or
  • your Project Theme

The latter applies if you are theming a component that is not or will not be published.

Build the CSS

Building a themed FrontendComponent is no different from building a FrontendComponent with normal LESS files inside.

  1. Install the following modules in the root of your project:
  • less-css-stream
  • parcelify

and if you haven't yet: browserify

  1. Then, inside the FrontendComponent that contains LESS files, specify the transform inside package.json, as well as the name(s) of the stylesheets that the parcelify plugin should pick up:
// gwi-modal/package.json

"style": "index.less",
"transforms": [ "less-css-stream" ]

The style key accepts a string or an array. Globs can be used.

  1. In your build command in the root of the project you would have something like this:
    browserify -p [ parcelify -o dist/bundle.css ] ./src/bootstrap.js > ./dist/main.js

Contribute

Owner: @gwildu Repository: https://gitlab.com/gwildu/gwi-theming.git