| npm i [email protected] |
| before(function () { | |
| global.document = jsdom(`<!doctype html><html><body><div id="container"/></div></body></html>`) | |
| global.window = document.defaultView | |
| }) | |
| after(function () { | |
| delete global.window | |
| delete global.document | |
| }) |
| let server | |
| before((done) => { | |
| const app = express() | |
| app.use('/', express.static(path.resolve(__dirname, '../../dist'))) | |
| server = app.listen(8080, done) | |
| }) | |
| after(() => { | |
| server.close() | |
| }) |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| var istanbul = require('istanbul'), | |
| gulp = require('gulp'), | |
| istanbul = require('gulp-istanbul'); | |
| gulp.task('js', function() { | |
| return gulp.src('js') | |
| .pipe(istanbul({ | |
| includeUntested: true, | |
| coverageVariable: '__coverage__' | |
| })) |
| .particleJs | |
| background-color transparent | |
| width 35% | |
| height 100% | |
| display block | |
| position absolute | |
| top 0px | |
| left 0px |
| 'use strict'; | |
| // simple express server | |
| var express = require('express'); | |
| var app = express(); | |
| var router = express.Router(); | |
| app.use(express.static('public')); | |
| app.get('/', function(req, res) { | |
| res.sendfile('./public/index.html'); |
This entire guide is based on an old version of Homebrew/Node and no longer applies. It was only ever intended to fix a specific error message which has since been fixed. I've kept it here for historical purposes, but it should no longer be used. Homebrew maintainers have fixed things and the options mentioned don't exist and won't work.
I still believe it is better to manually install npm separately since having a generic package manager maintain another package manager is a bad idea, but the instructions below don't explain how to do that.
Installing node through Homebrew can cause problems with npm for globally installed packages. To fix it quickly, use the solution below. An explanation is also included at the end of this document.
| var array = []; | |
| function closest(array,num){ | |
| var i=0; | |
| var minDiff=1000; | |
| var ans; | |
| for(i in array){ | |
| var m=Math.abs(num-array[i]); | |
| if(m<minDiff){ | |
| minDiff=m; |
