| if (!angular.merge) { | |
| angular.merge = (function mergePollyfill() { | |
| function setHashKey(obj, h) { | |
| if (h) { | |
| obj.$$hashKey = h; | |
| } else { | |
| delete obj.$$hashKey; | |
| } | |
| } |
| // ==UserScript== | |
| // @name Gmail: show full email addresses | |
| // @namespace http://mail.google.com/ | |
| // @match *://*mail.google.com/* | |
| // @exclude https://mail.google.com/*view=btop* | |
| // @exclude https://accounts.google.com/* | |
| // @version 0.3 | |
| // @description Gmail: showing full email addresses | |
| // @copyright 2013+, Luckylooke | |
| // ==/UserScript== |
| // ==UserScript== | |
| // @name Ebay GBP to EUR | |
| // @namespace http://example.com/ | |
| // @match *://*ebay.co.uk/* | |
| // @version 0.1 | |
| // @description converts all prices in GBP on site to EUR | |
| // @copyright 2012+, Luckylooke | |
| // ==/UserScript== | |
| GM_log('script "Ebay GBP to EUR" is running'); |
| // rewriten from http://sanojian.github.io/cellauto/ | |
| function CellAutoVoronoiCell(index) { | |
| this.index = index; | |
| this.delays = []; | |
| } | |
| CellAutoVoronoiCell.prototype.process = function(neighbors) { | |
| return; | |
| }; |
| // install latest stable node | |
| nvm install stable | |
| // install yoman | |
| npm install -g yo | |
| // yoman automaticly check enviroment via yoman doctor, copypaste sugested command into terminal | |
| echo "export NODE_PATH=$NODE_PATH:/home/ubuntu/.nvm/versions/node/v5.3.0/lib/node_modules" >> ~/.bashrc && source ~/.bashrc | |
| // you can check again that everything is OK now | |
| yo doctor |
| <!doctype html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>Pure JS spinner</title> | |
| <style> | |
| #spinner { font-size: 6em; } | |
| </style> | |
| </head> |
How to design library the most efficient way?
I have an idea about ideal lib design. But seems to be not easy to achieve it. I want to support [standard ES6 module], also other common use cases supported by [UMD]. BUT there is one more use case I want to support and so there is where the problem begins. I want to be able to switch parts of a library to different implementation.
The library is provided as pure standard ES6 module, without UMD or similar bundler specific wraps.
| // ==UserScript== | |
| // @name Aliexpress feedback | |
| // @namespace https://feedback.aliexpress.com/ | |
| // @version 1.1.0 | |
| // @description prefill 5-star rating in aliexpress feedback | |
| // @author luckylooke | |
| // @match https://feedback.aliexpress.com/management/leaveFeedback.htm* | |
| // @grant none | |
| // ==/UserScript== |
| // ==UserScript== | |
| // @name Aliexpress - precheck order detail | |
| // @namespace https://aliexpress.com/ | |
| // @version 1.0.0 | |
| // @description precheck checkboxes in order detail | |
| // @author luckylooke | |
| // @match https://trade.aliexpress.com/order_detail.htm* | |
| // @grant none | |
| // ==/UserScript== |
| function execute(action, callback) { | |
| // create real promise, because execute method does not return the real one | |
| // (missing documentation what actually returns) | |
| const promise = new Promise((resolve, reject) => { | |
| grecaptcha.ready(() => | |
| grecaptcha.execute(key, { action }).then(token => { | |
| resolve(token); | |
| }, | |
| reject) | |
| ); |