ag_dubs

18 ms·

1.
System dependencies are hard (so we made them easier)(blog.axo.dev)
3 points by ag_dubs 3y ago|0 comments
2.
Not every developer wants to be a web developer: hello oranda(blog.axo.dev)
4 points by ag_dubs 3y ago|0 comments
3.
Thanks for breaking cargo-dist (I rewrote it)(blog.axo.dev)
6 points by ag_dubs 4y ago|0 comments
4.
by ag_dubs 4y ago
definitely inspired by goreleaser! it's a great project
5.
by ag_dubs 4y ago
we actually agree and are working on this! github releases are just an easy initial target, and makes our tool a drop-in replacement for the kinds of things people are already doing. longer-term we'd like to see something more robust,
6.
Release engineering is exhausting so here's cargo-dist(blog.axo.dev)
262 points by ag_dubs 4y ago|63 comments
7.
Making calls to WebAssembly fast and implementing anyref(blog.benj.me)
68 points by ag_dubs 8y ago|6 comments
8.
by ag_dubs 8y ago
there's a human readable version, you can read more about it here: https://developer.mozilla.org/en-US/docs/WebAssembly/Underst...
9.
by ag_dubs 8y ago
fwiw as a former npm registry engineer i can tell u that "hundreds of download every month" likely is a result of the background bot activity npm gets. but your advice is sound! definitely vet your deps before you use them! and YE
10.
Announcing Free Orgs at npm(blog.npmjs.org)
5 points by ag_dubs 9y ago|1 comments
11.
Npm releases free orgs(go.npm.me)
2 points by ag_dubs 9y ago|0 comments
12.
Some notes on RFCs(blog.npmjs.org)
1 points by ag_dubs 10y ago|0 comments
13.
Npm5, specifications, and our RFC process(blog.npmjs.org)
2 points by ag_dubs 10y ago|0 comments
14.
Zero One Infinity READMEs(blog.npmjs.org)
1 points by ag_dubs 10y ago|0 comments
15.
by ag_dubs 10y ago
a few points! fwiw, only 2 of those humans work on the CLI, (3 if you count their manager, who spends a lot of time managing). other people work in sales, marketing, engineering on the website, engineering the registry, community + docs, et
16.
by ag_dubs 10y ago
that registry is a mirror of npm's registry. the mirror contains all package data but does not include any of the permissions or user management, so this tool still depends on npm infra for both that, and as a replication source.
17.
by ag_dubs 10y ago
ied didn't work on windows because of the linking strategy. many people who need to use npm use windows.
18.
by ag_dubs 10y ago
actualyl at this point, unless there is a legal request or a serious security issue, we don't allow any unpublishes. we encourage transferring the package to the npm user and deprecating it. yay immutable registry!
19.
by ag_dubs 10y ago
hi! they are running a mirror of the npm registry which contains all the package data but none of the permissions/user mgmt. this means that they are still dependent on npm infrastructure. npm, Inc strongly encourages people to build a
20.
Npm package tarball outage post-mortem(blog.npmjs.org)
2 points by ag_dubs 10y ago|0 comments
21.
Programmatically access all the public npmjs registry data: a tutorial(github.com)
1 points by ag_dubs 10y ago|0 comments
22.
by ag_dubs 10y ago
> a serious thundering herd hehe yup, def want to avoid that > Are the costs of npm public? Is it mostly bandwidth costs for transferring the tarballs? the costs aren't but that's an interesting idea. i'll bring it up w
23.
by ag_dubs 10y ago
greenkeeper uses the follower ^__^
24.
by ag_dubs 10y ago
we're still playing around with how many hooks to give each account- and we're definitely open to increasing it. this is why we're releasing in beta. as for it being paid, our registry is super expensive to run, so we're
25.
by ag_dubs 10y ago
we do have something called the registry follower ( https://github.com/npm/concurrent-couch-follower ) that can help you achieve a similar outcome, but hooks provides more specificity around certain events and is also si
26.
by ag_dubs 10y ago
this would primarily be for people who use their own internal packages in developing their own applications, i.e. a single author owns both packages. that being said, it turns out that the semver handshake the community does works Most of T
27.
by ag_dubs 11y ago
you might also consider the fact that OSX machines are expensive. and the education for learning linux is generally expensive or not accessible. so supporting windows also supports ... poor people, people from different countries that have
28.
by ag_dubs 11y ago
forcing a single copy of a dep is exactly the opposite of the dependency strategy both the node module loader and npm take. the fact that the node module loader can load more than one version of a module into memory is its strength and np
29.
by ag_dubs 11y ago
as the person who wrote these docs-- if you have questions or things you'd like to see addressed, i'd really love if you filed issues on the repo. https://github.com/npm/docs/issues
30.
by ag_dubs 11y ago
hi! i totally know this is a common feel for many npmjs users. this is why i've been running an empathy campaign for Windows, Windows Wednesday, where i do all my work (with/for npm) on windows. it's been good for finding bug

More ›