Matt Lockyer

@alex-zhang alternative?

the parcel dev server is fine, it's only the build process which I'm assuming calls @parcel/optimizer-cssnano

I had an error in my secret, it was not parsing correctly as JSON. Ironically, can't be detected by `wrangler build`, only found it when trying `wrangler publish`, and `wrangler...

any issues with this regex allowing any symbols? or don't care? e.g. `/[a-zA-Z0-9]{1,64}/.test('test@(*%^(*@%^#(%@test')`

WIP branch here Basically if: https://github.com/near/near-api-js/blob/43022551758e9a4b934b0156f5058dd36644bebe/src/wallet-account.ts#L205-L209 Then do this: https://github.com/near/near-api-js/blob/43022551758e9a4b934b0156f5058dd36644bebe/src/wallet-account.ts#L115-L128 tests passed, still need to conduct e2e testing, ETA EOD 07/25 or will have to be 07/28

@vgrichina still haven't had time to e2e test this, but what do you think of the approach so far? This should redirect to the wallet and we can include all...

I agree. This has bugged me quite a bit. near dev-deploy For example also fails (sometimes silently depending on your setup) if this config file specifies an object that contains...

@MaximusHaximus you're right I was aiming to reduce but we're now talking about a contract with arbitrary callbacks. If links were distributed with some complicated callback logic it would be...

Validators who have NEVER made it to the active set / proposals are still unable to be staked to. A simple fix when the user enters validator in the UI...

Only have support to check accountId is whitelisted: https://github.com/near/core-contracts/tree/master/whitelist