npm v5 ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸ - from scratch
npm v5 The npm Blog — v5.0.0 npm ã« v5 ãŒã‚„ã£ã¨ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã—ãŸã€‚ã“ã® npm v5 ã¯æ—¢ã«æ˜Žæ—¥ãƒªãƒªãƒ¼ã‚¹äºˆå®šã® Node v8 ã«ãƒãƒ³ãƒ‰ãƒ«ã•ã‚Œã‚‹äºˆå®šã§ã™ã€‚ ã‹ã„ã¤ã¾ã‚“ã§ã€æ©Ÿèƒ½ã‚’紹介ã—ã¾ã™ã€‚ Notable Changes package-lock.json!!! faster than npm v4 no more --save option Offline mode sha512 support package-lock.json!!! npm v4 ã¾ã§å•é¡Œã ã£ãŸ npm-shrinkwrap ã®å•é¡Œ を解消ã™ã‚‹ãŸã‚ã®æ–°ã—ã„ lock ファイルãŒç”Ÿã¾ã‚Œã¾ã—ãŸã€‚ shrinkwrap ã¯ä¾å˜ãƒ©ã‚¤ãƒ–ラリを固定ã™ã‚‹ãŸã‚ã®æ©Ÿèƒ½ã§ã™ã€‚npm v4 ã¾ã§ã¯ shrinkwrap ã§å›ºå®šã—ã¦ã„ã¾ã—ãŸãŒã€æ–°ã—ã npm v5 ã«ãªã£ã¦ã‹ã‚‰ã¯shrinkwrap ã¯
npm cache: the unsung hero
By Siddharth Kshetrapal I love npm and believe that this package manager is the single biggest reason for JavaScript’s massive success these past few years. There was a lot of excitement in the JavaScript community when facebook released yarn. And for good reason. Yarn’s install speeds are amazing. Subsequent installs are even faster because yarn caches installed modules on your machine. Install s
Lerna を使ã£ã¦ã€ Babel ã‚„ React ãŒæŽ¡ç”¨ã—ã¦ã„ã‚‹ monorepo を試ã—ã¦ã¿ã‚‹ - Qiita
monorepo ã¨ã¯ 複数㮠npm package ã‚’ å˜ä¸€ã® git repository ã§ç®¡ç†ã™ã‚‹ã“㨠例ãˆã° Babel ã§ã¯ã€ 100 以上㮠npm package ãŒå˜ä¸€ã® git repository ã§ç®¡ç†ã•ã‚Œã¦ã„ã‚‹ https://github.com/babel/babel/tree/master/packages package 毎㫠repository ã‚’ä½œã‚‹å ´åˆã¨æ¯”較ã—㟠Pros & Cons Babel ã® repository ã®ãƒ‰ã‚ュメントã‹ã‚‰æŠœç²‹ Pros: lint, build, test, release ã®ãƒ—ãƒã‚»ã‚¹ã‚’共通化ã§ãã‚‹ package ã‚’ã¾ãŸãŒã£ãŸä¿®æ£ãŒå®¹æ˜“ã«ãªã‚‹ issue 管ç†ã‚’一元化ã§ãã‚‹ 開発環境ã®æ§‹ç¯‰ãŒç°¡å˜ã«ãªã‚‹ テストも package ã‚’ã¾ãŸã„ã§å®Ÿè¡Œã§ãã€è¤‡æ•° package ãŒçµ¡ã‚€ä¸å…·åˆã®æ¤œçŸ¥ãŒå®¹æ˜“ã«ãªã‚‹ Con
NPM vs Yarn Cheat Sheet
Okay, so you’ve heard about this new JavaScript package manager called yarn, installed it with npm i -g yarn, and now you want to know how to use it? For the most part if you know NPM, you’re already set! Here are the key notes for switching. 👠Feel free to bookmark this article, as it will update often as yarn grows. Cheat Sheet — What you need to knownpm install === yarn Install is the default
Yarnファーストインプレッション - Qiita
Yarn ã¨ã¯ åå‰ã‹ã‚‰ yet another ... ãªé›°å›²æ°—を漂ã‚ã›ã¦ã¾ã™ãŒã€ npmäº’æ› ã§ã™ã€‚(追記: æ£ç¢ºã«ã¯npmã®ç”Ÿæˆã™ã‚‹package.jsonã¨äº’æ›ã¨ã®ã“ã¨ã ã£ãŸ)。å„所ã‹ã‚‰ node連ä¸ã¯ã¾ãŸãƒ„ール増やã—ã‚„ãŒã£ã¦ï¼ã¨ã„ã†é›°å›²æ°—ã‚’æ„Ÿã˜ã‚‹ã®ã§ã€ã“ã“ã¯æ˜Žç¢ºã«ã—ãŸæ–¹ãŒã„ã„。(techcrunchã®è¨˜äº‹ã¨ã‹ãã†ã„ã†å°è±¡ã‚’与ãˆã‚‹æ›¸ãæ–¹ã«ãªã£ã¦ã‚‹) npm install 時ã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªé…ç½®ã¸ã®ä»‹å…¥ npm install 時ã®ã‚ˆã‚Šè³¢ã„ãƒãƒ¼ã‚«ãƒ«ã‚ャッシュ yarn.lock ファイルã§ãƒãƒ¼ã‚¸ãƒ§ãƒ³å›ºå®š yarn 環境下㧠yarn add, yarn install ãªã©ã‚’è¡Œã£ãŸå ´åˆã€ yarn.lock 㨠package.json ã«åŒæ™‚ã«æ›¸ãè¾¼ã¿ã€ ãã®ç’°å¢ƒã§ç”Ÿæˆã•ã‚ŒãŸãƒ•ã‚¡ã‚¤ãƒ«ã¯ yarn ãªã—ã§ã‚‚å‹•ãã¾ã™ã€‚ã¤ã¾ã‚Šã€yarn ã¯ã‚ˆã‚ŠåŽ³å¯†ã« npm ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’固定ã—ãŸã„人å‘
Why I'm Working on Yarn
(This post is about Yarn, a new JS package manager that was announced today.) I work with Node and npm packages almost every day, on Tilde's main app, Skylight, or on one of Ember's many packages. Many have remarked upon how fast the npm registry has grown, and it's hard to imagine working on any of my packages without the npm ecosystem. I've also worked on a couple of application-level package ma
Yarn: A new package manager for JavaScript
In the JavaScript community, engineers share hundreds of thousands of pieces of code so we can avoid rewriting basic components, libraries, or frameworks of our own. Each piece of code may in turn depend on other pieces of code, and these dependencies are managed by package managers. The most popular JavaScript package manager is the npm client, which provides access to more than 300,000 packages
npm-scripts 㧠Web フãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰é–‹ç™ºã‚’管ç†ã™ã‚‹ - アカベコマイリ
gulp ãªã—ã® Web フãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰é–‹ç™ºã‹ã‚‰ 1 å¹´ã‚ã¾ã‚Šã€‚ãã®é–“ã€ç‰¹ã«å•é¡Œã‚‚ãªã npm-scripts 㧠Web フãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰é–‹ç™ºã‚’管ç†ã§ãã¦ã„ã‚‹ã®ã§ã€ã“ã®é–“ã«å¾—られãŸé‹ç”¨çŸ¥è¦‹ã‚„所感ãªã©ã‚’ã¾ã¨ã‚ã¦ã¿ã‚‹ã€‚ npm-scrips ã¨ã¯ï¼Ÿ 最近㮠Web フãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰é–‹ç™ºã§ã¯ AltJS/AltCSSã®ãƒ“ルドやリリース用イメージ作æˆãªã©ã« Node.js + npm を利用ã™ã‚‹ã“ã¨ãŒä¸€èˆ¬åŒ–ã—ã¦ããŸã€‚ãã®ãŸã‚プãƒã‚¸ã‚§ã‚¯ãƒˆã¯ package.json ã§ç®¡ç†ã™ã‚‹ã“ã¨ã«ãªã‚‹ã€‚package.json ã®æä¾›ã™ã‚‹ä»£è¡¨çš„ãªæ©Ÿèƒ½ã¨ã—㦠プãƒã‚¸ã‚§ã‚¯ãƒˆæƒ…å ±ã®å®šç¾© プãƒã‚¸ã‚§ã‚¯ãƒˆã®æˆæžœç‰©ã‚’ npm ã¨ã—ã¦é…布ã™ã‚‹ãŸã‚ã®æƒ…å ± プãƒã‚¸ã‚§ã‚¯ãƒˆåã€ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã€ä½œè€…ãªã©ã®ãƒ¡ã‚¿ãƒ‡ãƒ¼ã‚¿ã‚’定義ã™ã‚‹ ä¾å˜ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ç®¡ç† プãƒã‚¸ã‚§ã‚¯ãƒˆãŒä¾å˜ã™ã‚‹ npm ã¨ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’管ç†ã™ã‚‹ ã“ã®æƒ…å ±ã¸åŸºã¥ã npm install コ
npms
Your browser is out-of-date! Update your browser to view this website correctly. Update my browser now ×
The licenses in the npm-registry from their package.json, from the latest version of each module 23.11.2013
npm-registry-licenses.txt �' 說 The licenses in the npm-registry from their package.json, from the latest version of each module 23.11.2013 [ { key: 'undefined', value: 27785 }, { key: 'MIT', value: 20811 }, { key: 'BSD', value: 5240 }, { key: 'BSD-2-Clause', value: 621 }, { key: 'Apache 2.0', value: 263 }, { key: 'GPL', value: 233 }, { key: 'COUNTED DUAL-LICENSE', value: 224 }, { key: 'WTFPL', val
What Happened When I Peeked Into My Node_Modules Directory
Photo: Mint Images/Getty ImagesThe left-pad fiasco shook the JavaScript community to its core when a rouge developer removed a popular module from npm, causing tens of projects to go dark. While code bloat continues to slow down our websites, drain our batteries, and make “npm install†slow for a few seconds, many developers like myself have decided to carefully audit the dependencies we bring int
毎週ã®ã‚ˆã†ã«ä¾å˜ãƒ‘ッケージを上ã’続ã‘る努力 - CARTA TECH BLOG
皆ã•ã‚“ã“ã‚“ã«ã¡ã¯ã€‚fluctã«ã¦fluct SSPã¨ã„ã†åºƒå‘Šé…信システムã®ç®¡ç†ç”»é¢ã‚’ä¸å¿ƒã«ã‚¯ãƒ©ã‚¤ã‚¢ãƒ³ãƒˆã‚µã‚¤ãƒ‰ã®é–‹ç™ºã‚’è¡Œã£ã¦ãŠã‚Šã¾ã™ã€å¤§é–¢ã§ã™ã€‚ ä¾å˜ãƒ‘ッケージã®æ›´æ–°ã€ã©ã†ã—ã¦ã¾ã™ã‹ï¼Ÿ 今や数多ãã®è¨€èªžã§ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ãŒæä¾›ã•ã‚Œã¦ãŠã‚Šã€ã¿ãªã•ã‚“も日常的ã«ã‚³ãƒŸãƒ¥ãƒ‹ãƒ†ã‚£ã«ã‚ˆã‚‹ãƒ‘ッケージエコシステムを活用ã—ã¦ã„ã‚‹ã“ã¨ã¨æ€ã„ã¾ã™ã€‚ ã§ã™ãŒã€ã“ã®ä¾å˜ãƒ‘ッケージã®æ›´æ–°ã«ã¤ã„ã¦ã¯ã€ã©ã®ã‚ˆã†ã«ã—ã¦ã„ã¾ã™ã‹ï¼Ÿã€€ã‚»ã‚ュリティfixãªã©ã‚’除ãã€ä»¥ä¸‹ã®ã‚ˆã†ãªã“ã¨ã«ãªã£ã¦ã„ã‚‹ã“ã¨ãŒå¤šã„ã®ã§ã¯ãªã„ã§ã—ょã†ã‹ï¼Ÿ ãƒãƒ¼ãƒ ã®ã€Œã„ã„人ã€ãŒé ‘å¼µã£ã¦æ›´æ–°ã—続ã‘ã‚‹ ãã®äººã®è¬Žã®æƒ…熱ãŒæ¶ˆãˆã‚‹ã¨æ›´æ–°ã•ã‚Œãªããªã£ã¦ã—ã¾ã† ãŸã¾ã«æ°—ãŒã¤ã„ãŸã‚‰é ‘張る 「ã„ã„人ã€ãŒé ‘張るタイプã®äºœç¨® æ°—ãŒä»˜ã‹ãªã‹ã£ãŸã‚‰æ›´æ–°ã•ã‚Œãªã„ æ›´æ–°ã¯ãƒªã‚¹ã‚¯ãªã®ã§å¡©æ¼¬ã‘ã«ã™ã‚‹ プãƒãƒ€ã‚¯ãƒˆã¯å®šæœŸçš„ã«ä½œã‚Šç›´ã™å‰æ CIã§ãƒ†ã‚¹ãƒˆã‚’回ã—続ã‘ã¦ã„ã‚‹ã®ã«æ›´æ–°ã—ãªã„ãªã‚“ã¦â€¦â€¦ã¨ãƒ¢ãƒ¤
builder
BuilderBuilder takes your npm tasks and makes them composable, controllable from a single point, and flexible. npm is fantastic for controlling tasks (via scripts) and general project workflows. But a project-specific package.json simply doesn't scale when you're managing many (say 5-50) very similar repositories. Enter Builder. Builder is "almost" npm, but provides for off-the-shelf "archetypes"
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Signed and certified packages · Issue #29 · node-forward/discussions
Advantages of bundledDependencies over normal dependencies in npm
'SEE LICENSE IN' and 'UNLICENSED' now banned, and no SPDX license for proprietary software. · Issue #8918 · npm/npm
what SPDX license should I use for private modules? · Issue #8773 · npm/npm
npm semantic version calculator
NPM 3.10.8 tries to install optional dep on unsupported platform when using npm-shrinkwrap.json · Issue #14042 · npm/npm
EnterJS
{{#tags}}- {{label}}
{{/tags}}