唯然 aladdin-add

Pure ESM package

The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

Use ESM yourself. (preferred)
Use 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.
If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
Stay on the existing version of the package until you can move to ESM.

How to create an HTTPS certificate for localhost domains

This focuses on generating the certificates for loading local virtual hosts hosted on your computer, for development only.

Do not use self-signed certificates in production ! For online certificates, use Let's Encrypt instead (tutorial).

When you create a npm package, remember it might be used in a browser or a server, or even a command line utility… For each package you create, please pay attention at what it will be used for:

Is it going to be used as a dependency to a nodejs application that is not bundled? (e.g. command line utilities)
Is it going to be used as a dependency to a nodejs application that is bundled? (e.g. AWS Lambdas)
Is it going to be used as a dependency to a browser application (always bundled)?.

In cases 2) and 3) you want to allow for tree shaking.
In cases 1) and 2) you want to benefit from the "ES6"/"ES next" features supported natively by nodejs.
In case 3) you also want to benefit from the native support of "ES6" from your browser.

Problem: How can we preprocess JavaScript (at build-time or on the server-side) so engines like V8 don't have to spend as much time in Parse? This is a topic that involves generating either bytecode or a bytecode-like-abstraction that an engine would need to accept. For folks that don't know, modern web apps typically spend a lot longer in Parsing & Compiling JS than you may think.

Yoav: This can particularly be an issue on mobile. Same files getting parsed all the time for users. Theoretically if we moved the parsing work to the server-side, we would have to worry about it less.
One angle to this problem is we all ship too much JavaScript. That's one perspective. We could also look at preprocessing.
We've been talking about this topic over the last few weeks a bit with V8. There were three main options proposed.
1. Similar to what optimize-js does. Identify IIFEs and mark them as such so the browser and VMs heuristics will catch them and do a better job than today. optimize-js only tackles IIFE bu

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

	/**
	* Converts paths defined in tsconfig.json to the format of
	* moduleNameMapper in jest.config.js.
	*
	* For example, {'@alias/': [ 'path/to/alias/' ]}
	* Becomes {'@alias/(.*)': [ '<rootDir>/path/to/alias/$1' ]}
	*
	* @param {string} srcPath
	* @param {string} tsconfigPath
	*/

	/**
	This is an ECMA-404 compliant JSON parser written in pure JS, with nice error
	reporting. It's not super useful since it's ridiculously slow compared to
	`JSON.parse()`, but I had fun writing it.

	ISC License

	Copyright (c) 2019 Ryan Grove <ryan@wonko.com>

	Permission to use, copy, modify, and/or distribute this software for any purpose

	// UPDATE: In 2023, you should probably stop using this! The narrow version of Safari that
	// does not support `nomodule` is probably not being used anywhere. The code below is left
	// for posterity.

	/**
	* Safari 10.1 supports modules, but does not support the `nomodule` attribute - it will
	* load <script nomodule> anyway. This snippet solve this problem, but only for script
	* tags that load external code, e.g.: <script nomodule src="nomodule.js"></script>
	*
	* Again: this will not prevent inline script, e.g.:

	npm set registry https://r.npm.taobao.org # 注册模块镜像
	npm set disturl https://npm.taobao.org/dist # node-gyp 编译依赖的 node 源码镜像

	## 以下选择添加
	npm set sass_binary_site https://npm.taobao.org/mirrors/node-sass # node-sass 二进制包镜像
	npm set electron_mirror https://npm.taobao.org/mirrors/electron/ # electron 二进制包镜像
	npm set ELECTRON_MIRROR https://cdn.npm.taobao.org/dist/electron/ # electron 二进制包镜像
	npm set puppeteer_download_host https://npm.taobao.org/mirrors # puppeteer 二进制包镜像
	npm set chromedriver_cdnurl https://npm.taobao.org/mirrors/chromedriver # chromedriver 二进制包镜像
	npm set operadriver_cdnurl https://npm.taobao.org/mirrors/operadriver # operadriver 二进制包镜像

	// Opens window with facebook share dialog.
	// Remember to include OpenGraph meta tags in the page with sharing copy.

	var url = "http://google.com";
	window.open('http://facebook.com/sharer/sharer.php?u='+encodeURIComponent(url), '', 'left=0,top=0,width=650,height=420,personalbar=0,toolbar=0,scrollbars=0,resizable=0');