Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
ronag
Follow
ronag
Follow
Achievements
Achievements
Highlights
- 2 discussions answered
Pinned
8,855 contributions in the last year
Less
More
Activity overview
Contribution activity
February 2022
Created 16 commits in 3 repositories
Created a pull request in nodejs/node that received 29 comments
events: simplify on implementation
Implement AsyncIterables using AsyncGenerator.
+92
−174
•
29
comments
Opened 2 other pull requests in 1 repository
nodejs/node
1
open
1
merged
Reviewed 26 pull requests in 2 repositories
nodejs/undici
14 pull requests
- test(fetch): add client maxRequestsPerClient error test
- Add missing ts import
- chore: ignore wasm file for npm publishing
- fix interceptor type
- fix(test): fix test skipping logic
- types: align RequestInit types with lib.dom.ts
- docs: expand mixins information, notate body reuse
- fix: incorrect http(s) regexp
-
feat(fetch): allow
manualredirect handling -
fix(fetch): prevent
Illegal invocationsof theFileLikeclass - feat: add asyn iterable section in doc
- chore(.husky): remove unnecessary .gitignore
- docs: add test commands in CONTRIBUTING.md
- docs: link to fetch test coverage issue
nodejs/node
12 pull requests
- stream: need to cleanup event listeners if last stream is readable
- lib: add FormData global when fetch is enabled
- fs: fix cb/sync writev empty array behavior
- stream: add more filter tests
- stream: add more forEach tests
- stream: revert map spec compliance
- fs: fix writev empty array error behavior
- stream: refactor streams
- events: simplify on implementation
- readline: simplify async iterable implementation
- lib: performance improvement on readline async iterator
- cluster: make kill to be just process.kill
Created an issue in Level/leveldown that received 2 comments
Operation ordering guarantee
Haven't been able to find a definitive answer on this. Does level down guarantee that writes are always visible for reads, in order. e.g. is the fo…
2
comments
Opened 3 other issues in 2 repositories
nodejs/undici
2
open
uNetworking/uWebSockets.js
1
open
Answered 1 discussion in 1 repository
248
contributions
in private repositories
Feb 1 – Feb 15