This is a mirror of pdfjs-dist, bundled and exposed as an ES module
npm install npm install @bundled-es-modules/pdfjs-dist
<html> | |
<h2>Semantic-UI Color Gist</h2> | |
<section> | |
<!-- this markup is render by script, but sassmeister seems to have trouble with that --> | |
<!-- type anything here to force sassmeister to render!! --> | |
asd | |
<div id="demo"> | |
</div> |
<html> | |
<!-- this markup is render by script, but sassmeister seems to have trouble with that --> | |
<!-- type anything here to force sassmeister to render!! --> | |
<h2>Bootstrap Color Gist</h2> | |
<section> | |
<div id="demo"></div> | |
</section> |
sass doesn't have the "relative" saturation option available in less | |
@function relative-sat($color, $amt) { | |
$h: hue($color); | |
$s: saturation($color); | |
$l: lightness($color); | |
$sRel: $s + ($s * ($amt / 100)); | |
@return hsl($h, $sRel, $l); | |
} |
This is a mirror of pdfjs-dist, bundled and exposed as an ES module
npm install npm install @bundled-es-modules/pdfjs-dist
robrez [Apr 19th at 7:31 AM] | |
in #general | |
is there an "okay" way to use an external css file as the content of a (style) dom-module? | |
3 replies | |
westbrook [6 days ago] | |
You'd have to do it in the build step, as opposed to the delivered files. There was a comment earlier this week about it, I think they referenced this as a good example of doing so with gulp (the sass part not being a requirement). | |
These are not competing technologies. Angular is a framework. Polymer is a library. Let’s skip comparing libraries / frameworks against other libraries / frameworks for a second (polymer or angular or react or meteor or backbone or mustache or express or jquery or dojo or kendo).
Web development is ever-evolving. Being in tune with state of the platform (HTML, HTTP, Javascript, CSS) is critical to helping teams choose what technology (or technologies) are the right fit for particular team/project, to be responsive to paradigm shifts and to stay ahead of the curve (or at least not behind it).
There are a handful game-changing platform changes that have occurred recently. For the purposes of this conversation, let’s touch on just a couple.
#squash commits / rebase or merge
##If needed add upstream
git remote -v
git remote add upstream https://github.com/repo/project.git
git fetch upstream
git rebase upstream/master
git rebase --interactive HEAD~2
#note: per stackoverflow "git pull --rebase upstream master is analogous to git fetch upstream && git rebase upstream/master"
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<title>Polymer Element Test Case</title> | |
<base href="//polygit.org/components/"> | |
<script src="webcomponentsjs/webcomponents-lite.js"></script> | |
<link rel="import" href="polymer/polymer.html"> | |
<dom-module id="x-template"> | |
<script> |
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<title>Polymer Element Test Case</title> | |
<base href="//polygit.org/components/"> | |
<script src="webcomponentsjs/webcomponents-lite.js"></script> | |
<link rel="import" href="polymer/polymer.html"> | |
<dom-module id="x-foo"> | |
<template> |