systemjs
yhtml
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
systemjs
-
Rails upgrade to angular 2
I would like to upgrade my existing Rails and Angular 1.x application. I'm following the ng-upgrade documentation and seeing that there are many dependencies including systemjs, typescript, tsd and a few other javascript libraries. Ideally there would be a angular-2 gem that would have all the dependencies but I'm not able to find that. Next I looked for gem's for each dependency but there isn't one for tsd.
-
Modern SPAs without bundlers, CDNs, or Node.js
There's also https://github.com/systemjs/systemjs if you want more of a ponyfill approach. FWIW bundlers also don't use the browser's functionality to load modules...
-
JS Modules
A module loader interprets and loads a module written in a certain module format at runtime. Popular examples are RequireJS and SystemJS.
yhtml
-
If Web Components are so great, why am I not using them?
The main reason is that they're too low-level to use directly.
They do a lot, but stop just short of being useful without something of a framework on top. I tried hard to use them directly, but found that it was untenable without sensible template interpolation, and without helpers for event binding.
Here's my shot at the smallest possible "framework" atop Web Components that make them workable (and even enjoyable) as an application developer:
https://github.com/dchester/yhtml
It's just ~10 SLOC, admittedly dense, but which make a world of difference in terms of usability. With that in place, now you can write markup in a style not too dissimilar from React or Vue, like...
${this.count}
-
Modern SPAs without bundlers, CDNs, or Node.js
I also sometimes enjoy this approach of starting from absolutely nothing.
Instead of taking the path of starting with DOM manipulation and then going to a framework as necessary, I've kept really trying to make raw web components work, but kept finding that I wanted just a little bit more.
I managed to get the more I wanted -- sensible template interpolation with event binding -- boiled down to a tag function in 481 bytes / 12 lines of (dense) source code, which I feel like is small enough that you can copy/paste it around and not feel to bad about it. It's here if anyone cares to look: https://github.com/dchester/yhtml
- Bytes HTML tag function for rendering Web Component templates
What are some alternatives?
RequireJS - A file and module loader for JavaScript
fastdom - Eliminates layout thrashing by batching DOM measurement and mutation tasks
browserify - browser-side require() the node.js way
custom-elements - Using custom elements
script.js - Asyncronous JavaScript loader and dependency manager
img-comparison-slider - Image comparison slider. Compare images before and after. Supports React, Vue, Angular.
di4js - The di4js module is dependency injection implementation in JavaScript.
custom-elements-everywhere - Custom Element + Framework Interoperability Tests.
HeadJS - The only script in your HEAD.
proposal-import-attributes - Proposal for syntax to import ES modules with assertions
SeaJS - A Module Loader for the Web
FunPizzaShop