Note,
The following was first published by Sindre Sorhus in Jan 13 2021 at https://blog.sindresorhus.com/get-ready-for-esm-aa53530b3f77 but have since disappeard from the Internet. Thus republishing it below --
JavaScript Modules will soon be a reality for Node.js package maintainers.
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
import foo from 'foo' instead of const foo = require('foo') to import the package. You also need to put "type": "module" in your package.json and more. Follow the below guide.await import(…) from CommonJS instead of require(…).
| // @return Promise<boolean> | |
| async function askWritePermission() { | |
| try { | |
| // The clipboard-write permission is granted automatically to pages | |
| // when they are the active tab. So it's not required, but it's more safe. | |
| const { state } = await navigator.permissions.query({ name: 'clipboard-write' }) | |
| return state === 'granted' | |
| } catch (error) { | |
| // Browser compatibility / Security error (ONLY HTTPS) ... | |
| return false |
Steps to deploy a Node.js app to DigitalOcean using PM2, NGINX as a reverse proxy and an SSL from LetsEncrypt
If you use the referal link below, you get $10 free (1 or 2 months) https://m.do.co/c/5424d440c63a
I will be using the root user, but would suggest creating a new user
| const express = require('express'); | |
| const multer = require('multer'); | |
| const app = express(); | |
| const router = express.Router(); | |
| const path = require('path'); | |
| const Storage = multer.diskStorage({ | |
| destination: './public/images', | |
| filename: (req, file, cb) => { | |
| const fileName = |
| var canvas = document.createElement('canvas'); | |
| var gl; | |
| var debugInfo; | |
| var vendor; | |
| var renderer; | |
| try { | |
| gl = canvas.getContext('webgl') || canvas.getContext('experimental-webgl'); | |
| } catch (e) { | |
| } |
First, take a look at the ESLint rule documentation. Just skim it for now. It's very long and boring. You can come back to it later.
ESLint rules works on the AST (Abstract Syntax Tree) representation of the code. In short, this is a tree structure that describes the code in a very verbose form. ESLint walks this tree and rules can subscribe to be notified when it hits a specific node type, like a Literal type, which could be the "hello" part of const welcome = "hello";.
Go ahead and play around with some code in AST Explorer (Make sure the parser is espree). It's a great tool!
Here are some good articles on the subject (ignore the scaffolding parts):
| .force-show-scrollbars ::-webkit-scrollbar-track:vertical { | |
| border-left: 1px solid #E7E7E7; | |
| box-shadow: 1px 0 1px 0 #F6F6F6 inset, -1px 0 1px 0 #F6F6F6 inset; | |
| } | |
| .force-show-scrollbars ::-webkit-scrollbar-track:horizontal { | |
| border-top: 1px solid #E7E7E7; | |
| box-shadow: 0 1px 1px 0 #F6F6F6 inset, 0 -1px 1px 0 #F6F6F6 inset; | |
| } |
