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

mi2js

v1.0.0

Published

Component library

Downloads

1

Readme

mi2js

A JS/HMTL Component library, materializing slowly, trying to stay small by

  • adding useful features that do not require a lot of code
  • staying intentionally less advanced to reduce code-base
  • targeting back-ofice applications and not public web pages or websites to avoid many of horrible requirements forced onto public web (SEO, bullshit IE browser)
  • IE shit will still mostly work, and one can use polyfills for some cases, but certainly do not intend to clog this library with IE fixes

Guidelines

Some consideratoins (not necessarily strict rules) while making decisions in the code

  • create small and useful core
  • keep simple, short and independent
  • aim for less code in library (less bugs to make/test/fix)
  • implement/reimplement features in a way that makes application code simpler and more readable/understandable

Guidelines and future

  • remove features that are not essential (obviously this is influenced by personal preference)
  • split into small pieces to enable custom build with specific feature-set
  • consideing moving to ES6 syntax taht is transpiled to ES5
  • considering adding type-safety support without abandoning core JavaScript tricks I like to use (better FLow support looks like good direction)
  • I like Angular approach with directives, but am not fan of switching to TypeScriupt and also not fan of bi-directional binding

Code

  • clearing up the code documentation to generate nicer docs using jsdoc and also doclets.io
  • minimizer friendly
  • avoid too short variable names ( I tend to break this one often :D )
  • keep code for Web Components in JS files, no coding in HTML template (error handling becomes tedious, and code that interprets it gets complicated and large)
  • provide means to easily pinpoint error source (not just stack trace)

Browsers

Personally, I do not care about any browser without Flexbox support ( Flexbox is not actually required by the library )

  • Issues mostly easily fixable by polyfills
  • PhantomJS - polyfill for Function.bind is used
  • when printing HTML->PDF
  • testing using Karma
  • Chrome
  • Firefox
  • Fuck IE < 11
    • if it actually works on some old IE, zero F...s given
    • no plans to pollute library code for old browser support
  • Likely culprits for browser problems
  • Function.bind - known issue in PhantomJS
  • Object.create
  • hidden attribute - (IE <11) easily fixable with *[hidden] { display: none; !important}
  • Element.firstElementChild - same as nextElementSibling, previousElementSibling

License

See the LICENSE file for license rights and limitations (MIT).