The ESM standard is considered stable in NodeJS and well supported by a lot of modern JavaScript tools.
ESLint does a good job validating and fixing ESM code (as long as you don't use top-level await, coming in ESLint v8). Make sure to enable the latest ECMA features in the ESLint config.
{
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(…).
| #TabsToolbar { | |
| direction: rtl; | |
| } | |
| #tabbrowser-tabs { | |
| direction: ltr; | |
| } | |
| .titlebar-buttonbox { | |
| display: flex; |
| import _url from 'url'; | |
| const builtins = new Set( | |
| Object.keys(process.binding('natives')).filter(str => | |
| /^(?!(?:internal|node|v8)\/)/.test(str)) | |
| ); | |
| const esmIfExplicit = url => { | |
| const eof = url.slice(-5); | |
| return { |
| #!/usr/bin/env python | |
| ''' Run from "electrum/lib" directory. | |
| ThomaxV started a discussion on https://bitcointalk.org/index.php?topic=274182.msg2939599#msg2939599 | |
| about changing the HD derivation logic in electrum 2. The below post: | |
| http://bitcoin.stackexchange.com/questions/37013/how-to-import-a-hd-wallet-from-an-extended-private-key | |
| confirms that the format is actually m/c/i (and not m/44'/0'/a'/c/i) | |
| so I have altered https://gist.github.com/romanz/4b32782bfc0ff4984713 accordingly: | |
| tested to work with keys/addresses exported from electrum 2.7.0 | |
| note Electrum has a "gap limit" of 20, so loop @ level "c" to get the next 20 addresses | |
| ''' |
This is a guide that I wrote to improve the default security of my website https://fortran.io , which has a certificate from LetsEncrypt. I'm choosing to improve HTTPS security and transparency without consideration for legacy browser support.
I would recommend these steps only if you have a specific need for information security, privacy, and trust with your users, and/or maintain a separate secure.example.com domain which won't mess up your main site. If you've been thinking about hosting a site on Tor, then this might be a good option, too.
The best resources that I've found for explaining these steps are https://https.cio.gov , https://certificate-transparency.org , and https://twitter.com/konklone
| # -*- coding: utf-8 -*- | |
| """ | |
| wakatime.amqp | |
| ~~~~~~~~~~~~~ | |
| Setup for Celery distributed task queue. | |
| """ | |
| import socket |
| # use with: curl -L https://raw.github.com/gist/3426227 | bash | |
| # get git binary, then git with git | |
| sudo apt-get install git -y | |
| git clone https://github.com/git/git.git | |
| # remove your binary/package | |
| sudo apt-get remove git -y | |
| sudo apt-get install make checkinstall libcurl4-gnutls-dev libexpat1-dev gettext libz-dev libssl-dev asciidoc -y |