Vercel: Build and deploy the best web experiences with the Frontend Cloud – Vercel
Your complete platform for the web.Vercel provides the developer tools and cloud infrastructure to build, scale, and secure a faster, more personalized web. Your complete platform for the web.Vercel provides the developer tools and cloud infrastructure to build, scale, and secure a faster, more personalized web.
npm3 â“
OSS開発ã«ãŠã‘ã‚‹åˆæ„å½¢æˆã«JavaScriptã§å‚åŠ ã—ã€å¤‰åŒ–ã‚’èµ·ã“ã™ / front-end-lounge-1
npm update -g npm
npm command mini tips and news for front-end developer at CodeGrid 3rd anniversary party in Tokyo
Why my team uses npm instead of bower
tl;drMy team moved away from Bower because: Programmatic usage was painfulIts interface kept changingSome features, like the url shorthand, are entirely brokenUsing both bower and npm in the same project is painfulKeeping bower.json version field in sync with git tags is painfulSource control != package managementCommonJS support is not straightforwardSubstantive discussionMy team builds an SDK fo
npm Blog Archive: Welcome, jQuery developers!
The npm blog has been discontinued. Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog. Big news! jQuery recently put up a notice that its plugin registry is in read-only mode and that everyone who wants to publish a plugin should publish to npm. Lots of developers have already been publishing their jQuery packages to npm, so while the recent developments were
npm Blog Archive: npm's year in numbers: 2014
The npm blog has been discontinued. Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog. A small part of my job at npm is to keep track of various performance metrics. This helps make sure our systems are working and aren’t hiding any slow-growing performance problems, that we are appropriately planning for future growth, and that our business goals as a company
ç´°ã‹ã™ãŽã¦ä¼ã‚らãªã„ package.json å°ãƒã‚¿ä¸‰é¸ - t-wadaã®ãƒ–ãƒã‚°
ã“ã‚“ã«ã¡ã¯ã€å’Œç”° (@t_wada) ã§ã™ã€‚本日㯠Node.js Advent Calendar ã® 7 日目ã¨ã—ã¦ã€ Node.js ã§é–‹ç™ºã™ã‚‹éš›ã®è¨å®šãƒ•ã‚¡ã‚¤ãƒ« package.json ã«ã¾ã¤ã‚ã‚‹ Tips ã«ã¤ã„ã¦æ›¸ããŸã„ã¨æ€ã„ã¾ã™ã€‚ ã¯ã˜ã‚ã« ç§ã¯ã“ã‚Œã¾ã§ power-assert ã‚’ç†é ã«ã€ã„ãã¤ã‹ npm モジュールをリリースã—ã¦ãã¾ã—ãŸã€‚ Node.js を使ã£ãŸé–‹ç™ºã«ã¯ã€è¨å®šãƒ•ã‚¡ã‚¤ãƒ« package.json ã®è¨˜è¿°ãŒå¿…è¦ã§ã™ã€‚特㫠npm モジュールを公開ã™ã‚‹å ´åˆã«ã¯ã€è¨å®šã™ã¹ã事ã€è€ƒãˆã‚‹ã¹ã事もã„ã‚ã„ã‚増ãˆã¦ãã¾ã™ã€‚今回ã¯ã€ npm モジュールを作ã£ã¦ããŸéŽç¨‹ã§å¦ã‚“ã package.json ã«é–¢ã™ã‚‹ Tips ã®ä¸ã§ã€ã‚ã¾ã‚ŠçŸ¥ã‚‰ã‚Œã¦ã„ãªã„マイナー気味ãªã‚‚ã®ã‚’挙ã’ã¦ã„ããŸã„ã¨æ€ã„ã¾ã™ã€‚ Tips1: package.json ã® files フィールドã§ãƒ›ãƒ¯ã‚¤ãƒˆãƒªã‚¹
npm ã¨ãƒ•ãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰ã®ãƒ‘ッケージ管ç†ã®æœªæ¥
JavaScript 系パッケージマãƒãƒ¼ã‚¸ãƒ£ã®é‡è¤‡å•é¡Œ npm ã¯è¨€ã‚ãšã‚‚ãŒãª Node.js ã®ãƒ‘ッケージマãƒãƒ¼ã‚¸ãƒ£ã ãŒã€ãƒ•ãƒãƒ³ãƒˆã‚¨ãƒ³ãƒ‰é–‹ç™ºã«ãŠã„ã¦ã¯ Bower も利用ã™ã‚‹ã®ãŒä¸€èˆ¬çš„ã«ãªã£ã¦ã„る。ã“ã®ç¾çŠ¶ã®å•é¡Œç‚¹ã¯ã€package.jon 㨠bower.json ã¨ã„ã†ä¼¼ãŸã‚ˆã†ãªç®¡ç†ãƒ•ã‚¡ã‚¤ãƒ«ã‚’二é‡ã§ç®¡ç†ã—ãªã‘ã‚Œã°ãªã‚‰ãªã„ã¨ã„ã†ã“ã¨ã 。 ç¾çŠ¶ã®ä½¿ã„分ã‘ã‚’ãŠã•ã‚‰ã„ã‚’ã—ã¦ãŠãã¨ã€æ¬¡ã®ã‚ˆã†ãªæ„Ÿã˜ã«ãªã‚‹ã€‚ タスクランナー（Grunt/gulp）・モジュールシステム（browserify/webpack）・テストスイート（karma/testem）ãªã©ã®é–‹ç™ºç’°å¢ƒç³»ã®ç®¡ç†ãŒ npm ã®ä¸»ãªãŠä»•äº‹ã€‚インストールã•ã‚ŒãŸãƒ‘ッケージ㯠node_modules 内ã«å±•é–‹ã•ã‚Œã¦ã€CommonJS スタイルã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ç®¡ç†ã‹ã‚‰åˆ©ç”¨ã™ã‚‹ã€‚ 本題ã«ã¤ãªãŒã‚‹è©±ã¨ã—ã¦ã¯ã€ãƒ–ラウザã§å‹•ãライブラリã®ä¸€éƒ¨ã¯ npm ã«ã‚‚
AngularJS 1.3.0 – superluminal-nudge
Today, after eight months of work, over two thousand commits, nineteen beta and six release candidates, we finally released AngularJS 1.3.0 superluminal-nudge! This release includes many notable new features: One-time bindings – by prefixing an expression with "::", it will only be interpolated once, and then no longer watched. ngAria – a new module that helps make custom components in Angular mor
npm-scope
Scoped packages DESCRIPTION All npm packages have a name. Some package names also have a scope. A scope follows the usual rules for package names (url-safe characters, no leading dots or underscores). When used in package names, preceded by an @-symbol and followed by a slash, e.g. @somescope/somepackagename Scopes are a way of grouping related packages together, and also affect a few things about
npm Blog Archive: [email protected]
The npm blog has been discontinued. Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog. Last week, I released npm@2.0.0. If you’ve been using npm@1.4, it’s a substantial update, but that’s not why it’s 2.0.0. npm@1.0.1 was released on April 30th, 2011 – three and a half years ago. 1 That’s basically the entire lifetime of Node as a viable platform. Why bump the
NPM registry in numbers
Often in development you have to decide between a DIY solution or a few ready-made packages. Sometimes you might try to justify the answer by relying on the community choice, and usually it is a safe bet. For example, have you ever been asked to choose between underscore and lodash? Right on the front page of the npm registry there are some stats: Total Packages: 94 767Most dependent upon 7071 und
npmã®ã‚ã¾ã‚ŠçŸ¥ã‚‰ã‚Œã¦ãªã„機能 10é¸ - from scratch
ãªã‚“ã‹æœ€è¿‘Twitterã¨ã‹è·å ´ã§ã‚‚「npmã®æ©Ÿèƒ½ã§ãã‚“ãªã®ã‚ã£ãŸã‚“ã ã€ã£ã¦è¨€ã‚れるã“ã¨å¤šã„ã®ã§ã€èª¬æ˜Žã—ã¦ã„ãã¾ã™ã€‚ ã¡ãªã¿ã«ã‚¿ã‚¤ãƒˆãƒ«ã«ã¨ã‚Šã‚ãˆãš10é¸ã£ã¦æ›¸ã„ãŸã‘ã©ã€ã‚ã‚“ã¾ã‚ŠãŸãã•ã‚“æ€ã„ã¤ã„ã¦ãªã„ã®ã«ã€10é¸ã£ã¦æ›¸ã„ã¦ã—ã¾ã£ãŸã®ã§æœ€å¾Œã®æ–¹ã¯å¾®å¦™ã‹ã‚‚ã—ã‚Œã¾ã›ã‚“。 1. npm install㯠npm i ã§ã‚‚åŒã˜ã“ã¨ãŒã§ãã‚‹ ã¾ãå˜ç´”ãªã‚·ãƒ§ãƒ¼ãƒˆã‚«ãƒƒãƒˆã§ã™ã。isntallã¨ã‹typoã—ã¦ã¦ã‚‚空気èªã‚“ã§ãれるんã§ã™ãŒã€çŸã„ã»ã†ãŒã„ã„よãã£ã¦ã“ã¨ã§ã€‚ # npm installã£ã¦æ›¸ãã®ã‚‚ $ npm install socket.io #npm i ã£ã¦æ›¸ãã®ã‚‚åŒã˜ $ npm i socket.io # ã¡ãªã¿ã« --save㯠-S, --save-dev㯠-D ã«ã§ãã‚‹ $ npm i socket.io -S $ npm i mocha -Dショートカットå°ãƒã‚¿ã€‚ 2. npm
npm Blog Archive: The Future of the npm Website: Let's Map this Road!
The npm blog has been discontinued. Updates from the npm team are now published on the GitHub Blog and the GitHub Changelog. After announcing the complete rewrite of npm-www, many of you have asked what else was next for your favorite website. First, some data: Since January of this year, our web traffic has increased 47%. Approximately 35% of our visitors are coming to npmjs.org for the first tim
npm-Enterprise beta
npm Enterprise Beta npm Enterprise is an on-premise solution for managing private JavaScript modules, from the team that maintains npm and the public npm registry. Runs on your server or VM. Works with the standard npm client. Private namespaced modules to avoid name conflicts. Same patterns and tools developers love for open source. Seamless switching between private and open source projects. No
Choose: Grunt, Gulp, or npm?
A relevant ad will be displayed here soon. These ads help pay for my hosting. Please consider disabling your ad blocker on Pony Foo. These ads help pay for my hosting. Deciding on a technology is always hard. You don’t want to make commitments you won’t be able to back out of, but eventually you’ll have to make a choice and go for something that does what you need it to do. Committing to a build t
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
npm | build amazing things
bosco
requiring npm modules in the browser console
Modular frontend with NPM and pals
{{#tags}}- {{label}}
{{/tags}}