danilo neves cruz
danilo neves cruz
i could work it around using the following code: ```javascript const proxyquire = require('proxyquire'); const { expect } = require('chai'); const { firestore: { FieldPath } } = require('firebase-admin'); const...
same issue on npm community: https://npm.community/t/npm-ci-no-optional/6054
what about [power-assert-util-string-width](https://www.npmjs.com/package/power-assert-util-string-width)?
> * ... and we made sure that we have backward compatibility between OpenZeppelin 3.x and 4.x, so you could technically do such an upgrade if you need to add...
this is an example of an real test (flaky). currently we're using `provider.send("evm_setAutomine", [false])`, `provider.send("evm_setNextBlockTimestamp", [timestamp])` and then `provider.send("hardhat_mine", ["0x2", "0x0"])` to include new transactions, but the small timestamp difference...
@fvictorio not exactly. what i want is to `evm_setNextBlockTimestamp(x)`, then send+mine some transactions and at the end, `block.timestamp` is still `x` that i set initially.
decoupling would be the best. if not decoupled, i think it would be better to list it in [`optionalDependencies`](https://docs.npmjs.com/cli/v6/configuring-npm/package-json#optionaldependencies). i personally don't like `optionalDependencies` as they are not easy to...
> > i personally don't like optionalDependencies as they are not easy to opt-out, > > Could you explain this a bit further? What problems do you run into? there...
https://github.com/dapphub/dapptools/issues/820 is this issue related?
i'm having the same issue. any workaround?