juliangruber
Repos
781
Followers
1511
Following
202

A wrapper for abstract-leveldown compliant stores, for Node.js and browsers.

4035
252

Peer to peer data syncronization [ DEPRECATED - More info on active projects and modules at https://dat-ecosystem.org/ ]

646
68

📡 A free service that makes it easy for open-source Electron apps to update themselves.

452
55

Run code inside a browser from the command line

420
55

Brace expansion, as known from sh/bash, in JavaScript

173
24

Node 18's node:test, as an npm package

65
7

Events

Please update your v2 tag to the latest release

The v2 tag now refers to the v2.0.1 release. The latest release is v2.0.3, so please update your v2 tag.

Created at 2 hours ago
Please update your v2 tag to the latest release

I forgot to push tags, thank you!

Created at 2 hours ago
Add Wallet Backend. #388

For porting the logic to update/fetch transactions, I believe two things are necessary:

  1. Update the logic according to https://github.com/filecoin-station/filecoin-station/pull/373#discussion_r1087693320, so that we don't need to send updated state to the frontend while the function still executes, and only at the end
  2. Make the wallet backend stateful: The backend will have this.transactions = [], and use that to diff updates
Created at 3 hours ago
Add Wallet Backend. #388

There is one big missing piece though: automated tests.

Great point! I've followed your structure and ported as much as I could for now. Could you please take another look? The functions that I didn't port were too intertwined with electron/ipc/state logic. If you see ways to port more, could you please make specific suggestions?

We can't really test transferring funds, because

  • it takes too long (> 20 minutes)
  • the glif apis for testnet didn't work the same way as the mainnet ones
Created at 3 hours ago

test getSeedPhrase

test and refactor more

refactor getStateReplay

refactor getTipset

cleanup

Created at 3 hours ago
Add Wallet Backend. #388

The semantics are a bit different, because setInterval doesn't wait for doSomeWork to finish, and therefore can run multiple invocations at the same time. The 1:1 translation would be:

;(async () => {
  while (true) { 
    doSomeWork().catch(...)
    await timers.setTimeout(10_000)
  }
})()

To me this example shows how much more flexible this more native JS approach is

Created at 5 hours ago
started
Created at 1 day ago
issue comment
Testing modules

Is there a standard we want to adapt? Maybe deno's testing stdlib?

Created at 1 day ago