Skip to content
This repository was archived by the owner on May 18, 2021. It is now read-only.

Commit 848d944

Browse files
committed
npm-weekly #21
1 parent 4f6a116 commit 848d944

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

source/_drafts/npm-weekly-21.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
title: "npm 週報 #21 : npm 3 更新 + react.js 元件工具"
2+
date: 2015-06-26 15:14:32
3+
tags:
4+
categories: npm 週報
5+
---
6+
7+
8+
[Sign up](https://www.npmjs.com/npm-weekly) for the weekly.
9+
10+
## npm 3 beta testers
11+
12+
If you’re an npm@3 beta tester, be advised: the tags for downloading the latest and next versions of npm@3 have changed. They are now `[email protected]` and `[email protected]`. Checkout the [CHANGELOG](https://github.com/npm/npm/blob/master/CHANGELOG.md) for more info. Also, thank you to all of you for helping us squash all those bugs!
13+
14+
[Kat](https://twitter.com/maybekatz) also snuck a lot of things into npm@2 while [Forrest](https://twitter.com/othiym23) was away, so checkout those in the [CHANGELOG](https://github.com/npm/npm/blob/master/CHANGELOG.md#v2130-2015-07-02).
15+
16+
## npm 3 beta brings good news for windows users
17+
18+
[Rebecca](https://twitter.com/ReBeccaOrg) [talked to InfoQ](http://www.infoq.com/news/2015/06/npm) about npm@3, particularly how the changes to the installation process will help Windows users.
19+
20+
## private modules post-mortem
21+
22+
We’ve alerted private modules users via email, but in case you missed it there was a security issue with private modules last week. Metadata about private modules was leaked, but package contents and private user information were not. Read more in the [post-mortem](http://status.npmjs.org/incidents/6r2jr0dd9kd5).
23+
24+
## react podcast on webpack vs. browserify
25+
26+
If you’re working with React.js components, you’ll probably want to listen to the React Podcast on [Webpack vs Browserify](http://reactpodcast.com/2015/06/webpack-vs-browserify/) as tools for managing your front-end dependencies. The discussion starts around the 7-minute mark.
27+
28+
On the same subject, [Lin](https://twitter.com/linclark) explained how you can [use Browserify with npm (and Babel)](https://youtu.be/Tjwm9yPzBGg?t=6913) for front-end package management at jQuerySF last month and will be talking about Webpack at [React Rally](http://www.reactrally.com/) in August.
29+
30+
## npm is now my snippet database
31+
32+
In his AMA, [Sindre Sorhus](https://twitter.com/sindresorhus) explains how he uses npm as a way to [capture his code snippets](https://github.com/sindresorhus/ama/issues/10#issuecomment-117766328).
33+
34+
Why copy-paste when you can require it and with the benefit of having a clear intent. Fixing a bug in a snippet means updating one module instead of manually fixing all the instances where the snippet is used.
35+
36+
37+
原文:[npm Weekly, #21](http://blog.npmjs.org/post/123564120105/npm-weekly-21-npm-3-updates-react-js),作者:[@npm](http://blog.npmjs.org/),翻譯 [@iojs-tw](https://github.com/iojs/iojs-tw),授權 [CC-BY 4.0](https://creativecommons.org/licenses/by/4.0/deed.zh_TW)

0 commit comments

Comments
 (0)