An example that shows the difference between creating a JavaScript class and subclass in ES5 and ES6.
// source: https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/CustomEvent | |
;(function() { | |
if (typeof window.CustomEvent === "function") return false | |
function CustomEvent(event, params) { | |
params = params || { bubbles: false, cancelable: false, detail: undefined } | |
var evt = document.createEvent("CustomEvent") | |
evt.initCustomEvent(event, params.bubbles, params.cancelable, params.detail) | |
return evt | |
} |
<?php | |
$html = <<<HTML | |
<html> | |
<head> | |
<script src="http://example.com"></script> | |
</head> | |
<body> | |
<div> | |
<script> |
const {PassThrough} = require('stream')
const fs = require('fs')
const d = new PassThrough()
fs.createReadStream('tt2.js').pipe(d) // can be piped from reaable stream
d.pipe(process.stdout) // can pipe to writable stream
d.on('data', console.log) // also like readable
If you hate git submodule
, then you may want to give git subtree
a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add
command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this: