killa

Maybe a general api like `response.writeInfomation(statusCode, [, statusMessage][, headers])` for send 1xx response. If have this api, no need more api for new 1xx status code.

In some case, save tag is expected. Antd mark the stable version with `conch` dist-tag, when i install antd with `npm i antd@conch`, i also want save it with `conch`...

@ljharb We know */latest is bad practice, but in same case, we trust the tag, like `dev` tag or `stable` tag. So let we have the choice to use `--save-tag`...

Because the tag is generate by myself or platform i trust.

In the pre-release scenario,semver may not works well. If I have two dev branch, foo and bar, I'll release two version, 1.0.0-foo.alpha.0 and 1.0.0-bar.alpha.0. If ^1.0.0-foo.alpha.0 save to the package.json,...

The `bug fix`/`new feature` will release in a new version, but not know in dev stage. Do we have best practice for this scenario?

@ngot Use `ready` callback to confirm worker is ready, instead of check listening port. When use `nginxSticky` mode, workers listen different port, check port will not work.

@zweifisch 这个 PR 是想解决什么问题？

@tyouzu1 可以考虑一下 https://github.com/sofastack/sofa-hessian-node，提前把类型生成到 classmap 里就没有这个问题了。如果是 $class 这种写法，必须每次都把字端写全才可以。

> package 可能来自多个 registry，根路径是否考虑添加一下 packageId 字段？ 虽然会有多 registry 同步的问题，但是一个 registry 中 name 一定是唯一的，否则会有同名攻击。 > payload 默认返回全量信息，需要在 post 请求体的时候先判断一下 body 大小加个限制吗？ 这个暂时不考虑，未来可以在读取的时候做这个限制。