What is the "module" package.json field for?I've seen some npm packages (vue for example) have a module field in their package.json. But module is not included in the package.json documentation - is this a convention of some kind? Is there documentation for this somewhere?
Introducing npx: an npm package runner
[You can also read this post in Russian.] Those of you upgrading npm to its latest version, npm@5.2.0, might notice that it installs a new binary alongside the usual npm: npx. npx is a tool intended to help round out the experience of using packages from the npm registry — the same way npm makes it super easy to install and manage dependencies hosted on the registry, npx makes it easy to use CLI t
escope
Escope (escope) is ECMAScript scope analyzer extracted from esmangle project. Example var escope = require('escope'); var esprima = require('esprima'); var estraverse = require('estraverse'); var ast = esprima.parse(code); var scopeManager = escope.analyze(ast); var currentScope = scopeManager.acquire(ast); // global scope estraverse.traverse(ast, { enter: function(node, parent) { // do stuff if (
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
GitHub - yahoo/fetchr: Universal data access layer for web applications.
GitHub - eslint/typescript-eslint-parser: An ESLint custom parser which leverages TypeScript ESTree to allow for ESLint to lint TypeScript source code.
