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

prophet-xcss

v1.1.6

Published

a simple css parser for desktop and mobile using express

Downloads

19

Readme

npm version npm download

prophet-xcss

This has nothing to do with xCSS! I just came up with the same name and noticed it was already taken later.

This is a very simple preprocessor library for express to use different css styles for desktop and mobile.

prophet-xcss is completely backwards compatible with regular css.

In order to use this library, you simply have to include it in your express server like this:

const express = require('express')
const xcss = require('prophet-xcss')
const app = express()

app.use(xcss(['.', './css'])) 
//Include all directories, where you want to use prophet-xcss. 
//File paths can be absolute or relative! 

You can now write both desktop and mobile styles in your css, by just seperating them with a +

body{
    background-color: red + blue;
    /*This is now going to be red on desktop and blue on mobile*/

    font-size: _ + 200%;
    /*Use a _ if you want the property to not exist on one platform.*/
}

This gets served to a desktop user as

body{
    background-color: red;
}

To a mobile user it will look like this

body{
    background-color: blue;

    font-size: 200%;
}

You can also supply the paths lazily as functions. This allows you to either generate them lazily if getting your paths is somehow expensive. Additionally this can be used to dynamically change the directories you want to allow if you generate your css dynamically or something similar.

const express = require('express')
const xcss = require('prophet-xcss')
const app = express()

let mainDirectories = ['public', 'public/css']
const getOtherDirectories = () => otherDirectories.filter(x => x.includes('css'))

app.use(xcss([() => mainDirectories, () => otherDirectories])) 

mainDirectories.push('public/more_css')

Options

Fast Mode

app.use(xcss(['./css'], {fastMode:true}))
  • Fast mode is disabled by default.
  • Fast mode caches the final CSS, so it does not have to recalculate the css for each request.
  • This can especially improve performance if you have a lot of CSS.
  • You have to restart your server every time you make any changes to the CSS!

Verbose

app.use(xcss(['./css'], {verbose:true}))
  • The verbose flag is disabled by default.
  • Similar to the --verbose flag on a lot of cli-tools, it logs a lot of additional information to the console.
  • This might be useful for debugging, but verbose mode should NOT be used in production code!