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

web-browser-style

v0.1.2

Published

Web browser CSS utilities

Downloads

3

Readme

web-browser-style

Web browser CSS utilities.

Install

npm install web-browser-style --save

Use

  • px(value: number): string — Rounds the amount of pixels with a sensible precision and appends "px" at the end. Example: 123.456789"123.457px". Rounding could be used for less clutter in debugging and also for dealing with really big or really small numbers which could end up converted to a string using "exponential" format as "1.2345e-50", and when a web browser receives such a weird value for a pixels amount, it considers it invalid. And if such an "invalid" pixels amount is used as part of a "complex" CSS property like box-shadow then the whole such property gets discarded. The rationale for rounding precision being 3 here is that no screen could currently resolve up to a 1,000th fraction of a pixel.

  • scaleFactor(value: number): string — Rounds a tranform: scale() value with a sensible precision and converts to a string. Example: 123.456456456456456456456..."123.456456456". See the description of px() function for the rationale on rounding. The rationale for the rounding precision being about 10 here is that scaling a very high-resolution image to a single pixel should still be precise enough. So if an image has a width of 1,000,000,000px then in order to scale it to 1px the scale factor would be 1 / 1,000,000,000.

  • percent(value: number): string — Multplies the value by 100, rounds it with a sensible precision and converts it to a string while appending "%" at the end. Example: 1.23456456456456456456456..."123.456456456%". See the description of px() function for the rationale on rounding. The rationale for the rounding precision being about 10 here is that scaling a very high-resolution image to a single pixel should still be precise enough. So if an image has a width of 1,000,000,000px then in order to scale it to 1px the scale factor would be 1 / 1,000,000,000.

  • ms(value: number): string — Rounds the value with a sensible precision and converts it to a string while appending "ms" at the end. Example: 1.23456456456456456456456..."123.456ms". See the description of px() function for the rationale on rounding. The rationale for the rounding precision being about 3 here is that a human eye can't resolve at 1,000,000 frames per second.

  • getCssVariable(variableName: string): string — Returns the value for the specified CSS variable name.

  • getCssVariables(variableNames: string[]): string[] — Returns the values for the specified CSS variable names.

  • getDimensionalCalculatedCssVariable(variableName: string): string — Returns the value for the specified CSS variable name. This function could be used in cases when a CSS variable value is defined using a calc() function because in those cases the standard getCssVariable() function will return a value with a calc(). For example, getCssVariable() could return "calc(14px*3)" while getDimensionalCalculatedCssVariable() would return "42px". This function works by creating a new DOM element, inserting it into the document, measuring it and then removing it from the document.

Test

npm test

GitHub Ban

On March 9th, 2020, GitHub, Inc. silently banned my account (erasing all my repos, issues and comments) without any notice or explanation. Because of that, all source codes had to be promptly moved to GitLab. The GitHub repo is now only used as a backup (you can star the repo there too), and the primary repo is now the GitLab one. Issues can be reported in any repo.

License

MIT