Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add bignumber.js to web3-core (for its types) #3390

Merged
merged 3 commits into from
Feb 28, 2020
Merged

Add bignumber.js to web3-core (for its types) #3390

merged 3 commits into from
Feb 28, 2020

Conversation

cgewecke
Copy link
Collaborator

@cgewecke cgewecke commented Feb 24, 2020

Description

In #3213 @types/bignumber.js was removed - that package is now a stub and the main module implements its types internally.

However, bignumber.js is not a direct dependency here - it's only used for its types - and TS users currently see the error reported in #3386 about an unresolved import.

tsc tests did not catch this because bignumber.js exists in the development dependency tree.

bignumber.js is imported in

This PR should not affect the bundle size.

Fixes #3386

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • I have selected the correct base branch.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no new warnings.
  • Any dependent changes have been merged and published in downstream modules.
  • I ran npm run dtslint with success and extended the tests and types if necessary.
  • I ran npm run test:unit with success.
  • I have executed npm run test:cov and my test cases do cover all lines and branches of the added code.
  • I ran npm run build-all and tested the resulting file/'s from dist folder in a browser.
  • I have updated the CHANGELOG.md file in the root folder.
  • I have tested my code on the live network.

@coveralls
Copy link

coveralls commented Feb 24, 2020

Coverage Status

Coverage remained the same at 86.047% when pulling 8c7cd86 on issue/3386 into ccc229e on 1.x.

Copy link
Collaborator

@holgerd77 holgerd77 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, fix has also be confirmed here.

@holgerd77
Copy link
Collaborator

Hmm, Travis is failing after I updated the branch.

@holgerd77
Copy link
Collaborator

holgerd77 commented Feb 25, 2020

Update: CI already failed after merging #3376

@cgewecke
Copy link
Collaborator Author

@holgerd77 I think Travis or mocha just ran one of the jobs too slowly - this happens fairly often :) It's possible to restart the job from the Travis UI using a button next to the failing item - usually passes second time.

The "allowed failure" windows job (always times out) looks ok for this PR - it's running as expected and exiting 0 here.

@nivida nivida added 1.x 1.0 related issues Review Needed Maintainer(s) need to review Types Incorrect or missing types labels Feb 28, 2020
@holgerd77 holgerd77 merged commit a6ddec5 into 1.x Feb 28, 2020
@holgerd77 holgerd77 deleted the issue/3386 branch February 28, 2020 13:02
@cgewecke cgewecke mentioned this pull request Mar 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.x 1.0 related issues Review Needed Maintainer(s) need to review Types Incorrect or missing types
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Typescript compilation error regarding a bignumber.js import
4 participants