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

slicky

v2.0.1

Published

Light JS framework combining features of angular 2 and spine.js together.

Downloads

42

Readme

NPM version Dependency Status Build Status

Donate

Slicky

Light JS framework combining features of angular 2 and spine.js together.

The problem of mine...

I have some really large application written in PHP and we definitely don't plan changing whole application into SPA. But the thing is that we need some JS, because 21st century right? And yes, it's also good for our users.

Currently we are using angular 1, but the problem is that it's really overcomplicated. If you don't know what I mean, please watch this video from ng-conf 2015 where Misko Hevery and Rado Kirov explained syntax and differences between angular 1 and angular 2.

So after trying angular 2 on one test project for a month, I really wanted to try it on our website also. Problem is that I can't... Angular 2 basically works just with SPA websites. Hmm... What now? I can stick with angular 1, but I can't really say that I'm 100% sure about the code I write. Or use something like backbone (too old) or eg. spine.js which we used before angular 1 (I don't like CoffeScript anymore).

That's why I created yet another JS framework.

When to use it

  • When you have large server side application
  • When you think angular 2 is really awesome
  • When you want something really simple
  • When you want to use typescript
  • When you want add some JS behavior to existing site
  • When you don't need jquery

When not use it

  • When you want single page application (just go with angular 2)
  • When you want just some jquery

Installation

$ npm install slicky
$ npm install es7-reflect-metadata

Next steps

  1. bootstrap
  2. directives
  3. components
  4. templating
  5. communication between components
  6. filters
  7. dependency injection
  8. translations
  9. life cycle events
  10. ElementRef
  11. Extensions