Edit — best to first try:
mariadb-secure-installation -u $(whoami)
Original version here below in case the above does not work for you.
Edit — best to first try:
mariadb-secure-installation -u $(whoami)
Original version here below in case the above does not work for you.
{ | |
"name": "workshop-setup", | |
"version": "1.0.0", | |
"description": "This is the common setup script for most of my workshops", | |
"bin": "./setup.js" | |
} |
A Pen by Adam Quinton on CodePen.
var keepsHisWord; | |
keepsHisWord = true; | |
promise1 = new Promise(function(resolve, reject) { | |
if (keepsHisWord) { | |
resolve("The man likes to keep his word"); | |
} else { | |
reject("The man doesnt want to keep his word"); | |
} | |
}); | |
console.log(promise1); |
if ('NodeList' in window && !NodeList.prototype.forEach) { | |
console.info('polyfill for IE11'); | |
NodeList.prototype.forEach = function (callback, thisArg) { | |
thisArg = thisArg || window; | |
for (var i = 0; i < this.length; i++) { | |
callback.call(thisArg, this[i], i, this); | |
} | |
}; | |
} |
prettier-eslint |
eslint-plugin-prettier |
eslint-config-prettier |
|
---|---|---|---|
What it is | A JavaScript module exporting a single function. | An ESLint plugin. | An ESLint configuration. |
What it does | Runs the code (string) through prettier then eslint --fix . The output is also a string. |
Plugins usually contain implementations for additional rules that ESLint will check for. This plugin uses Prettier under the hood and will raise ESLint errors when your code differs from Prettier's expected output. | This config turns off formatting-related rules that might conflict with Prettier, allowing you to use Prettier with other ESLint configs like eslint-config-airbnb . |
How to use it | Either calling the function in your code or via [prettier-eslint-cli ](https://github.co |
/* | |
Incredibly simple Node.js and Express application server for serving static assets. | |
DON'T USE THIS IN PRODUCTION! | |
It is meant for learning purposes only. This server is not optimized for performance, | |
and is missing key features such as error pages, compression, and caching. | |
For production, I recommend using an application framework that supports server-side rendering, | |
such as Next.js. https://nextjs.org |
server { | |
listen 80; | |
server_name kirby.dev www.kirby.dev; | |
root /path/to/www/kirby; | |
access_log /var/log/nginx/access.log; | |
error_log /var/log/nginx/error.log; | |
# Route LetsEncrypt ACME Challenges to the right place | |
location ^~ /.well-known/acme-challenge/ { |
const transitionToPromise = (el, property, value) => | |
new Promise(resolve => { | |
el.style[property] = value; | |
const transitionEnded = e => { | |
if (e.propertyName !== property) return; | |
el.removeEventListener('transitionend', transitionEnded); | |
resolve(); | |
} | |
el.addEventListener('transitionend', transitionEnded); | |
}); |
'use strict'; | |
var fs = require('fs'); | |
var gulp = require( 'gulp' ); | |
var modernizr = require('modernizr'); | |
var config = require('./modernizr-config'); // path to JSON config | |
gulp.task( 'modernizr', function (done) { | |
modernizr.build(config, function(code) { |